| 2.1 |
Approval of the agenda |
|
| R2-2206900 |
Agenda for RAN2#119-e |
Chairman |
| 2.2 |
Approval of the report of the previous meeting |
|
| R2-2206901 |
RAN2#118-e Meeting Report |
MCC |
| 2.4 |
Instructions |
|
| R2-2206902 |
RAN2 Handbook 08-22 |
MCC |
| 2.5 |
Others |
|
| R2-2208700 |
LS On UE capability signalling for IoT-NTN |
Nokia |
| R2-2208928 |
LS On UE capability signalling for IoT-NTN |
RAN2 |
| R2-2209175 |
Correction for QoE |
R3 (Ericsson, Samsung, Nokia, Nokia Shanghai Bell) |
| R2-2209176 |
Addition of a CHO-related notes to a chapter on HO with DC [CHOwithDCkept] |
R3 (Nokia, Nokia Shanghai Bell) |
| R2-2209177 |
Correction of MBS stage 2 |
R3 (Nokia, Nokia Shanghai Bell) |
| R2-2209178 |
CAG access control without mobility restrictions |
R3 (Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, Ericsson) |
| R2-2209179 |
CAG access control without mobility restrictions |
R3 (Huawei, Nokia, Nokia Shanghai Bell, Orange, Deutsche Telekom, Ericsson) |
| R2-2209180 |
Completion of the missing descripition of SCG MRO handling |
R3 (Nokia, Nokia Shanghai Bell, ZTE) |
| R2-2209181 |
Clarification on direct data forwarding for MN initiated CPC to TS37340 |
R3 (ZTE, Lenovo, CATT, Huawei, Intel Corporation) |
| R2-2209182 |
Correction on Slice Group Configuration |
R3 (CMCC, Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, CATT) |
| R2-2209183 |
Correction for TS 38.300 on UHI in MR-DC |
R3 (ZTE, Lenovo, China Unicom) |
| R2-2209184 |
Support for flexible gNB ID length [gNB_ID_Length] |
R3 (Huawei, Qualcomm Incorporated, Ericsson, Nokia, Nokia Shanghai Bell) |
| R2-2209223 |
Coordination of CHO and intra-SN SCG reconfiguration |
R3 (ZTE, Nokia, Nokia Shanghai Bell, Huawei, Ericsson, Intel Corporation, CATT) |
| 3 |
Incoming liaisons |
|
| R2-2206970 |
LS on Priority given to Rel-17 LSs from CT (CP-221319; contact: Orange) |
CT1 |
| 4.1 |
NB-IoT and eMTC corrections Rel-16 and earlier |
|
| R2-2207312 |
Clarification on schedulingInfoList for in NB-IoT |
MediaTek Inc. |
| R2-2207313 |
Clarification on schedulingInfoList for in NB-IoT |
MediaTek Inc. |
| R2-2207314 |
Clarification on schedulingInfoList for in NB-IoT |
MediaTek Inc. |
| R2-2208594 |
36331_(R16)_Clarification on SPS deactivation upon carrier reconfiguration |
ZTE Corporation, Sanechips |
| R2-2208595 |
36331_(R17)_Clarification on SPS deactivation upon carrier reconfiguration |
ZTE Corporation, Sanechips |
| R2-2208712 |
Report of [AT119-e][202][LTE] LTE legacy CRs, eMTC/NB-IoT (MediaTek) |
MediaTek |
| R2-2208942 |
Clarification on schedulingInfoList in NB-IoT |
MediaTek Inc |
| R2-2208943 |
Clarification on schedulingInfoList in NB-IoT |
MediaTek Inc |
| R2-2208944 |
Clarification on schedulingInfoList in NB-IoT |
MediaTek Inc |
| R2-2209096 |
36331_(R16)_Clarification on SPS deactivation upon carrier reconfiguration |
ZTE Corporation, Sanechips |
| R2-2209097 |
36331_(R17)_Clarification on SPS deactivation upon carrier reconfiguration |
ZTE Corporation, Sanechips |
| R2-2209221 |
SPS deactivation upon carrier reconfiguration |
ZTE Corporation, Sanechips |
| R2-2209222 |
SPS deactivation upon carrier reconfiguration |
ZTE Corporation, Sanechips |
| 4.4 |
Other LTE corrections Rel-16 and earlier |
|
| R2-2207023 |
Correction on SCG failure information procedure |
ITRI |
| R2-2207024 |
Correction on SCG failure information procedure |
ITRI |
| R2-2207025 |
Correction on SCG failure information procedure |
ITRI |
| R2-2207391 |
Corrections on CHO recovery |
CATT |
| R2-2207392 |
Corrections on CHO recovery |
CATT |
| R2-2208531 |
Miscellaneous changes collected by Rapporteur |
Samsung |
| R2-2208532 |
Miscellaneous changes collected by Rapporteur |
Samsung |
| R2-2208533 |
Miscellaneous changes collected by Rapporteur |
Samsung |
| R2-2208711 |
Report of [AT119-e][201][LTE] LTE legacy CRs, non-IoT (Samsung) |
Samsung |
| R2-2208997 |
Corrections on CHO recovery |
CATT |
| R2-2208998 |
Corrections on CHO recovery |
CATT |
| R2-2209026 |
Miscellaneous changes collected by Rapporteur |
Samsung |
| R2-2209027 |
Miscellaneous changes collected by Rapporteur |
Samsung |
| R2-2209028 |
Miscellaneous changes collected by Rapporteur |
Samsung |
| 5.1.1 |
Stage 2 and Organisational |
|
| R2-2206921 |
Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 (R1-2205465; contact: Huawei) |
RAN1 |
| R2-2206928 |
LS on New UE Feature for HARQ-ACK multiplexing on PUSCH in the absence of PUCCH (R1-2205634; contact: Apple) |
RAN1 |
| R2-2206952 |
Further Reply LS on configuration of p-MaxEUTRA and p-NR-FR1 (R4-2210815; contact: Qualcomm) |
RAN4 |
| R2-2207131 |
Clarification of PUCCH group definition |
OPPO |
| R2-2207134 |
Clarification of PUCCH group definition |
OPPO |
| R2-2207735 |
NR Correction related to RNA |
Deutsche Telekom, Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2207879 |
Correction on Stage 2 description of Access Control clauses |
Peraton Labs CISA ECD |
| R2-2208190 |
Clarification on PUCCH primary and secondary group definition |
Ericsson |
| R2-2208191 |
Clarification on PUCCH primary and secondary group definition |
Ericsson |
| R2-2208192 |
Clarification on PUCCH primary and secondary group definition |
Ericsson |
| R2-2208414 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Samsung |
| R2-2208418 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Samsung |
| R2-2208977 |
NR Correction related to RNA |
Deutsche Telekom, Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2208978 |
NR Correction related to RNA |
Deutsche Telekom, Huawei, HiSilicon, Nokia (Rapporteur) |
| R2-2209065 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Samsung |
| R2-2209066 |
Rapporteur Clean-up |
ZTE Corporation (Rapporteur), Sanechips, Samsung |
| R2-2209154 |
Reply LS on eMIMO features defined in different granularity with prerequisite (R1-2208250; contact: Huawei) |
RAN1 |
| R2-2209155 |
Reply LS on the CSI periodic reporting for Dormant SCell state (R1-2208258; contact: Samsung) |
RAN1 |
| R2-2209158 |
LS on intraBandENDC-Support (R4-2214411; contact: Huawei) |
RAN4 |
| 5.1.2 |
User Plane corrections |
|
| R2-2208969 |
[309][R15/16 UP] CRs on UP (Nokia) |
Nokia (Rapporteur) |
| 5.1.2.1 |
MAC |
|
| R2-2207896 |
Clarification on BFD while SCell is deactivated |
Nokia, Nokia Shanghai Bell |
| R2-2207897 |
Clarification on BFD while SCell is deactivated |
Nokia, Nokia Shanghai Bell |
| R2-2207898 |
Clarification on the matching TB size for 2-step RA |
Nokia, Nokia Shanghai Bell |
| R2-2207899 |
Clarification on the matching TB size for 2-step RA |
Nokia, Nokia Shanghai Bell |
| R2-2208008 |
SPS HARQ feedback dropping for TDD |
Nokia, Nokia Shanghai Bell |
| R2-2208009 |
Clarification on HARQ RTT timer in case of HARQ feedback dropping |
Nokia, Nokia Shanghai Bell |
| R2-2208010 |
Clarification on HARQ RTT timer in case of HARQ feedback dropping |
Nokia, Nokia Shanghai Bell |
| R2-2208011 |
Clarification on HARQ RTT timer in case of HARQ feedback dropping |
Nokia, Nokia Shanghai Bell |
| R2-2208024 |
Clarification on configuredGrantTimer and cg-RetransmissionTimer |
Nokia, Nokia Shanghai Bell |
| R2-2208025 |
Clarification on configuredGrantTimer and cg-RetransmissionTimer |
Nokia, Nokia Shanghai Bell |
| R2-2208254 |
Correction on RA Resource Selection in Rel-15 |
vivo |
| R2-2208261 |
Correction on RA Resource Selection in Rel-16 |
vivo |
| R2-2208263 |
Correction on RA Resource Selection in Rel-17 |
vivo |
| 5.1.2.2 |
RLC PDCP SDAP BAP |
|
| R2-2206980 |
Retransmission SDU choice under double-no condition When T-PollRetransmit expiration |
PML |
| R2-2208689 |
Correction on RLC retransmission SDU choice when T-PollRetransmit expiration |
Purple Mountain Laboratories |
| 5.1.3.1 |
NR RRC |
|
| R2-2208972 |
Report of [AT119-e][007][NR1516] RRC Conn Control I (Nokia) |
Nokia, Nokia Shanghai Bell |
| 5.1.3.1.1 |
Connection control |
|
| R2-2206918 |
Reply LS on power control for NR-DC (R1-2205448; contact: Nokia) |
RAN1 |
| R2-2206930 |
LS on NPN only cell (R3-223928; contact: Huawei) |
RAN3 |
| R2-2207139 |
Clarification on FR2 p-max parameters |
OPPO |
| R2-2207140 |
clarification on FR2 p-max parameters |
OPPO |
| R2-2207142 |
Clarification on powe sharing UE capability |
OPPO |
| R2-2207143 |
Clarification on powe sharing UE capability |
OPPO |
| R2-2207157 |
Reply LS on NPN only cell |
ZTE Corporation, Sanechips |
| R2-2207158 |
Consideration on the Target cell ID for the Short MAC I Calculation |
ZTE Corporation, Sanechips |
| R2-2207159 |
CR on Target Cell ID setting for the NPN-only Cell (R16) |
ZTE Corporation, Sanechips |
| R2-2207160 |
CR on Target Cell ID setting for the NPN-only Cell (R17) |
ZTE Corporation, Sanechips |
| R2-2207237 |
Cell Identity Issue for NPN during RRC Resume Procedure |
OPPO |
| R2-2207258 |
P-Max definition in SIB1 and dedicated signalling |
Nokia, Nokia Shanghai Bell |
| R2-2207259 |
P-Max definition in SIB1 and dedicated signalling |
Nokia, Nokia Shanghai Bell |
| R2-2207260 |
P-Max definition in SIB1 and dedicated signalling |
Nokia, Nokia Shanghai Bell |
| R2-2207261 |
Use of NS-values with intra-band UL CA |
Nokia, Nokia Shanghai Bell |
| R2-2207262 |
Use of NS_55 and NS_57 on band n77 |
Nokia, Nokia Shanghai Bell |
| R2-2207263 |
Correction to firstOFDMSymbolInTimeDomain |
Nokia, Nokia Shanghai Bell |
| R2-2207264 |
Correction to firstOFDMSymbolInTimeDomain |
Nokia, Nokia Shanghai Bell |
| R2-2207265 |
Correction to firstOFDMSymbolInTimeDomain |
Nokia, Nokia Shanghai Bell |
| R2-2207266 |
Correction to firstOFDMSymbolInTimeDomain |
Nokia, Nokia Shanghai Bell |
| R2-2207400 |
Correction to RLF configuration in case of DAPS HO |
Fujitsu |
| R2-2207401 |
Correction to RLF configuration in case of DAPS HO |
Fujitsu |
| R2-2207502 |
Discussion on NPN-only cell |
Huawei, HiSilicon |
| R2-2207503 |
Correction to 38.331 on NPN-only cell |
Huawei, HiSilicon |
| R2-2207504 |
Correction to 38.331 on NPN-only cell |
Huawei, HiSilicon |
| R2-2207550 |
NR DC Power control |
Nokia, Nokia Shanghai Bell |
| R2-2207551 |
NR DC Power control |
Nokia, Nokia Shanghai Bell |
| R2-2207552 |
NR DC Power control |
Nokia, Nokia Shanghai Bell |
| R2-2207553 |
NR DC Power control |
Nokia, Nokia Shanghai Bell |
| R2-2207603 |
Correction on NR-DC power control |
vivo |
| R2-2207604 |
Correction on NR-DC power control |
vivo |
| R2-2207605 |
Correction on NR-DC power control |
vivo |
| R2-2207606 |
Correction on NR-DC power control |
vivo |
| R2-2207941 |
Correction on the field description for highSpeedDemodFlag |
Huawei, HiSilicon |
| R2-2208058 |
Correction to add EHC context in UE Inactive AS context |
Huawei, HiSilicon |
| R2-2208059 |
Correction to add EHC context in UE Inactive AS context |
Huawei, HiSilicon |
| R2-2208139 |
NS_55/57 in NR CA |
Ericsson |
| R2-2208163 |
Correction for NS 55 and NS 57 and associated capability bits |
Ericsson |
| R2-2208164 |
Ensuring consistent support of capability bits and associated NS-values in n77 in USA and Canada |
Ericsson |
| R2-2208270 |
Correction of PUSCH repetition configuration |
Qualcomm Incorporated |
| R2-2208271 |
Correction of PUSCH repetition configuration |
Qualcomm Incorporated |
| R2-2208402 |
Clarification on headerCompression for DAPS bearer |
ZTE Corporation, Sanechips |
| R2-2208403 |
Clarification on headerCompression for DAPS bearer |
ZTE Corporation, Sanechips |
| R2-2208457 |
Correction on NR CA configruation for n77 [n77 USA/Canada] |
MediaTek Inc. |
| R2-2208473 |
Clarification on RLC bearer handling for fullConfig |
CATT |
| R2-2208474 |
Correction for field description on PUSCH |
MediaTek Beijing Inc. |
| R2-2208476 |
Correction for field description on PUSCH |
MediaTek Beijing Inc. |
| R2-2208550 |
CR on 38.331 for sn-FieldLength change for the case of bearer type change |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, CATT |
| R2-2208551 |
CR on 38.331 for sn-FieldLength change for the case of bearer type change |
ZTE Corporation, Sanechips,Nokia, Nokia Shanghai Bell, CATT |
| R2-2208552 |
CR on 38.331 for sn-FieldLength change for the case of bearer type change |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, CATT |
| R2-2208553 |
Considerations on sn-fieldlength change in the case of bearer type change |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, CATT |
| R2-2208579 |
38.331 cr(Rel-17) correction on the condition of configuring discardTimer |
Xiaomi |
| R2-2208580 |
38.331 cr(Rel-16) correction on the condition of configuring discardTimer |
Xiaomi |
| R2-2208581 |
38.331 cr(Rel-15) correction on the condition of configuring discardTimer |
Xiaomi |
| R2-2208691 |
Clarification on reestablishRLC for DAPS HO |
ZTE Corporation, Sanechips |
| R2-2208905 |
Cell Identity Issue for NPN during RRC Resume Procedure |
OPPO |
| R2-2208938 |
[AT119-e][032][NR1516] n77 (Ericsson) |
Ericsson |
| R2-2208954 |
Report for [AT119-e][009][NR1516] RRC Conn Control III (Huawei) |
Huawei, HiSilicon |
| R2-2208979 |
Clarification on powe sharing UE capability |
OPPO, Nokia, Nokia Shanghai Bell |
| R2-2208980 |
Clarification on powe sharing UE capability |
OPPO, Nokia, Nokia Shanghai Bell |
| R2-2208986 |
Correction on the field description for highSpeedDemodFlag |
Huawei, HiSilicon |
| R2-2209010 |
NR-DC Power Control |
Nokia, Nokia Shanghai Bell, OPPO |
| R2-2209011 |
NR-DC Power Control |
Nokia, Nokia Shanghai Bell, OPPO |
| R2-2209067 |
Clarification on headerCompression for DAPS bearer |
ZTE Corporation, Sanechips |
| R2-2209068 |
Clarification on headerCompression for DAPS bearer |
ZTE Corporation, Sanechips |
| R2-2209075 |
Correction for PUSCH-PowerControl field descriptions for 2-step RACH |
MediaTek Inc. |
| R2-2209076 |
Correction for PUSCH-PowerControl field descriptions for 2-step RACH |
MediaTek Inc. |
| R2-2209081 |
Report of [AT119-e][007][NR1516] RRC Conn Control I (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2209085 |
CR on 38.331 for sn-FieldLength change for the case of bearer type change |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, CATT |
| R2-2209086 |
CR on 38.331 for sn-FieldLength change for the case of bearer type change |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, CATT |
| R2-2209087 |
CR on 38.331 for sn-FieldLength change for the case of bearer type change |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, CATT |
| R2-2209095 |
Report of [AT119-e][008][NR1516] RRC Conn Control II (ZTE) |
ZTE Corporation (Rapporteur) |
| R2-2209099 |
Correction of PUSCH repetition configuration |
Qualcomm Incorporated |
| R2-2209100 |
Correction of PUSCH repetition configuration |
Qualcomm Incorporated |
| R2-2209140 |
Ensuring consistent support of capability bits and associated NS-values in n77 in USA and Canada |
Ericsson |
| 5.1.3.1.2 |
Other |
|
| R2-2207257 |
Clarification to expiry of IDLE mode measurements |
Nokia, Nokia Shanghai Bell |
| R2-2207547 |
SIB1 transmission period |
Nokia, Nokia Shanghai Bell |
| R2-2207548 |
SIB1 transmission period |
Nokia, Nokia Shanghai Bell |
| R2-2207549 |
SIB1 transmission period |
Nokia, Nokia Shanghai Bell |
| R2-2207560 |
Corrections on s-MeasureConfig in NR |
Samsung |
| R2-2207568 |
Corrections on s-MeasureConfig in NR |
Samsung |
| R2-2207574 |
Corrections on s-MeasureConfig in NR |
Samsung |
| R2-2207611 |
Disscussion on SI request issue |
vivo |
| R2-2207612 |
38331 CR on SI request |
vivo |
| R2-2207615 |
Discussion on the measurement during RRC connection establishment and RRC connection resume |
vivo |
| R2-2207616 |
Rel-15 331 CR on the measurement during RRC connection establishment and RRC connection resume |
vivo |
| R2-2207617 |
Rel-16 331 CR on the measurement during RRC connection establishment and RRC connection resume |
vivo |
| R2-2207618 |
Rel-17 331 CR on the measurement during RRC connection establishment and RRC connection resume |
vivo |
| R2-2208140 |
Miscellaneous non-controversial corrections Set XV |
Ericsson (Rapp), Lenovo |
| R2-2208202 |
Miscellaneous corrections |
Lenovo |
| R2-2208203 |
Miscellaneous corrections |
Lenovo |
| R2-2208265 |
Discussion on SI-request Period Issues |
vivo |
| R2-2208337 |
38331 CR on SI request |
vivo |
| R2-2208338 |
38331 CR on SI request |
vivo |
| R2-2208346 |
Corrections on measurement report triggering |
OPPO, ZEKU, ZTE |
| R2-2208347 |
Corrections on measurement report triggering |
OPPO, ZEKU, ZTE |
| R2-2208348 |
Corrections on measurement report triggering |
OPPO, ZEKU, ZTE |
| R2-2209062 |
Corrections on s-MeasureConfig in NR |
Samsung |
| R2-2209063 |
Corrections on s-MeasureConfig in NR |
Samsung |
| R2-2209064 |
Corrections on s-MeasureConfig in NR |
Samsung |
| R2-2209071 |
Summary of offline [011][NR1516] RRC LTE Overheating Misc and Idle |
Ericsson |
| R2-2209092 |
Report of [AT119-e][010][NR1516] RRC Other |
vivo |
| R2-2209259 |
Corrections on measurement report triggering |
OPPO, ZEKU, ZTE |
| R2-2209260 |
Corrections on measurement report triggering |
OPPO, ZEKU, ZTE |
| R2-2209261 |
Corrections on measurement report triggering |
OPPO, ZEKU, ZTE |
| 5.1.3.2 |
LTE changes |
|
| R2-2207357 |
SCG Overheating termination in EN-DC |
Samsung |
| R2-2207358 |
SCG Overheating termination in EN-DC |
Samsung |
| R2-2207575 |
Correction on NR serving frequency results reporting for event-triggered measurement (R15) |
Huawei, HiSilicon, OPPO, MediaTek Inc., vivo, Nokia, Nokia Shanghai Bell, CATT, Ericsson, NTT DOCOMO, Lenovo, ZTE Corporation, Apple, NEC, China Telecom |
| R2-2207576 |
Correction on NR serving frequency results reporting for event-triggered measurement (R16) |
Huawei, HiSilicon, OPPO, MediaTek Inc., vivo, Nokia, Nokia Shanghai Bell, CATT, Ericsson, NTT DOCOMO, Lenovo, ZTE Corporation, Apple, NEC, China Telecom |
| R2-2207577 |
Correction on NR serving frequency results reporting for event-triggered measurement (R17) |
Huawei, HiSilicon, OPPO, MediaTek Inc., vivo, Nokia, Nokia Shanghai Bell, CATT, Ericsson, NTT DOCOMO, Lenovo, ZTE Corporation, Apple, NEC, China Telecom |
| R2-2208207 |
Rel-16 Correction of overheating for NR SCG |
Qualcomm Incorporated, Ericsson |
| R2-2208208 |
Rel-17 Correction of overheating for NR SCG |
Qualcomm Incorporated, Ericsson |
| R2-2208209 |
Rel-15 Clarification on the overheating UAI |
Qualcomm Incorporated |
| R2-2208210 |
Rel-16 Clarification on the overheating UAI |
Qualcomm Incorporated |
| R2-2208211 |
Rel-17 Clarification on the overheating UAI |
Qualcomm Incorporated |
| R2-2209251 |
Correction of overheating for NR SCG |
Qualcomm Incorporated, Ericsson |
| R2-2209252 |
Correction of overheating for NR SCG |
Qualcomm Incorporated, Ericsson |
| 5.1.3.3 |
UE capabilities |
|
| R2-2206911 |
Reply LS on PDCCH Blind Detection in CA (R1-2205320; contact: Huawei) |
RAN1 |
| R2-2207049 |
On early implementation and capability signaling of Power Class 1.5 |
MediaTek Inc. |
| R2-2207085 |
PC1.5 and legacy power class capability reporting clarification |
MediaTek Inc. |
| R2-2207086 |
PC1.5 and legacy power class capability reporting clarification |
MediaTek Inc. |
| R2-2207094 |
Make PC1.5 an early implementation candidate |
MediaTek Inc. |
| R2-2207095 |
Make PC1.5 an early implementation candidate |
MediaTek Inc. |
| R2-2207113 |
Clarification on codebookParametersPerBC parameter for extension of CSI-RS capabilities reporting |
MediaTek Inc. |
| R2-2207114 |
Clarification on codebookParametersPerBC parameter for extension of CSI-RS capabilities reporting |
MediaTek Inc. |
| R2-2207331 |
Correction on beamManagementSSB-CSI-RS |
Qualcomm Incorporated |
| R2-2207332 |
Correction on beamManagementSSB-CSI-RS |
Qualcomm Incorporated |
| R2-2207640 |
CR to TS 38.306 on UE capability of MMSE-IRC receiver |
China Telecom |
| R2-2207641 |
CR to TS 38.306 on UE capability of MMSE-IRC receiver |
China Telecom |
| R2-2208027 |
Correction on crossCarrierA-CSI-trigDiffSCS-r16 (38.306) |
Ericsson |
| R2-2208028 |
Correction on crossCarrierA-CSI-trigDiffSCS-r16 (38.306) |
Ericsson |
| R2-2208501 |
Correction on PDCCH Blind Detection capability in CA |
Huawei, HiSilicon |
| R2-2208502 |
Correction on PDCCH Blind Detection capability in CA |
Huawei, HiSilicon |
| R2-2208503 |
Correction on PDCCH Blind Detection capability in CA |
Huawei, HiSilicon |
| R2-2208504 |
Correction on PDCCH Blind Detection capability in CA |
Huawei, HiSilicon |
| R2-2208505 |
Clarification on pusch-RepetitionTypeA-r16 capability |
Huawei, HiSilicon |
| R2-2208506 |
Clarification on pusch-RepetitionTypeA-r16 capability |
Huawei, HiSilicon |
| R2-2208991 |
CR to TS 38.306 on UE capability of MMSE-IRC receiver |
China Telecom |
| R2-2208992 |
CR to TS 38.306 on UE capability of MMSE-IRC receiver |
China Telecom |
| R2-2209019 |
Report of [AT119-e][012][NR1516] UE capabilities (MediaTek) |
MediaTek |
| R2-2209055 |
Correction on PDCCH blind detection capability in CA |
Huawei, HiSilicon |
| R2-2209056 |
Correction on PDCCH blind detection capability in CA |
Huawei, HiSilicon |
| R2-2209057 |
Correction on PDCCH blind detection capability in CA |
Huawei, HiSilicon |
| R2-2209058 |
Correction on PDCCH blind detection capability in CA |
Huawei, HiSilicon |
| R2-2209059 |
Clarification on pusch-RepetitionTypeA-r16 capability |
Huawei, HiSilicon |
| R2-2209060 |
Clarification on pusch-RepetitionTypeA-r16 capability |
Huawei, HiSilicon |
| R2-2209069 |
Correction on crossCarrierA-CSI-trigDiffSCS-r16 (38.306) |
Ericsson |
| R2-2209070 |
Correction on crossCarrierA-CSI-trigDiffSCS-r16 (38.306) |
Ericsson |
| R2-2209131 |
Clarification on codebookParametersPerBC parameter for extension of CSI-RS capabilities reporting |
MediaTek Inc. |
| R2-2209132 |
Clarification on codebookParametersPerBC parameter for extension of CSI-RS capabilities reporting |
MediaTek Inc. |
| R2-2209133 |
Make PC1.5 an early implementation candidate |
MediaTek Inc. |
| R2-2209134 |
Make PC1.5 an early implementation candidate |
MediaTek Inc. |
| R2-2209148 |
Report of [AT119-e][012][NR1516] UE capabilities (MediaTek) |
MediaTek |
| 5.1.3.4 |
Idle and inactive mode procedures |
|
| R2-2207540 |
UE behavior when IMS emergency call is not supported in cell |
Samsung |
| R2-2207558 |
UE behavior when IMS emergency call is not supported in cell |
Samsung |
| R2-2207559 |
UE behavior when IMS emergency call is not supported in cell |
Samsung |
| 5.2.1 |
General and Stage-2 corrections |
|
| R2-2206905 |
Reply LS on V2X PC5 link for unicast communication with null security algorithm (C1-223972; contact: Huawei) |
CT1 |
| R2-2206950 |
Reply LS on signalling of PC2 V2X intra-band con-current operation (R4-2210733; contact: CATT) |
RAN4 |
| R2-2206975 |
Reply LS on V2X PC5 link for unicast communication with null security algorithm (S3-221590; contact: Lenovo) |
SA3 |
| R2-2209160 |
LS on Pemax,c of S-SSB transmission when multiple resource pool is configured in a carrier (R4-2214421; contact: vivo) |
RAN4 |
| 5.2.2 |
Control plane corrections |
|
| R2-2207217 |
Correction on null security algorithm |
ZTE Corporation, Sanechips |
| R2-2207218 |
Correction on null security algorithm |
ZTE Corporation, Sanechips |
| R2-2207219 |
(draft)reply LS on null security algorithm |
ZTE Corporation, Sanechips |
| R2-2208045 |
Miscelleneous CR on 38.331 |
Huawei, HiSilicon |
| R2-2208046 |
Miscelleneous CR on 38.331 |
Huawei, HiSilicon |
| R2-2208049 |
Draft reply LS on V2X PC5 link for unicast communication with null security algorithm |
Huawei, HiSilicon |
| R2-2208050 |
Clarification on PC5 AS security |
Huawei, HiSilicon |
| R2-2208051 |
Clarification on PC5 AS security |
Huawei, HiSilicon |
| R2-2208052 |
Summary on Rel-16 control plane corrections |
Huawei, HiSilicon |
| R2-2208217 |
Clarifications on PC5 UE capabilities for V2X |
Nokia, Nokia Shanghai Bell |
| R2-2208284 |
Clarification of NULL security algorithm |
Samsung Electronics Co., Ltd |
| R2-2208287 |
Clarification of NULL security algorithm |
Samsung Electronics Co., Ltd |
| R2-2208350 |
Correction on LCID assignment for SL LCH |
ASUSTeK |
| R2-2208351 |
Correction on LCID assignment for SL LCH |
ASUSTeK |
| R2-2208600 |
Correction on Missing UE behavior on sidelink reset |
vivo |
| R2-2208601 |
Correction on Missing UE behavior on sidelink reset |
vivo |
| R2-2208831 |
Clarification of NULL security algorithm |
ZTE, Samsung, vivo |
| R2-2208832 |
Reply LS on null security algorithm |
RAN2 |
| R2-2208833 |
Summary of [501] |
ZTE |
| R2-2208834 |
Miscellaneous CR on 38.331 |
Huawei, HiSilicon (Rapporteur) |
| R2-2208835 |
Miscellaneous CR on 38.331 |
Huawei, HiSilicon (Rapporteur) |
| R2-2208836 |
Summary of [AT119-e][502][V2X/SL] 38.331 corrections (Huawei) |
Huawei, HiSilicon |
| R2-2208837 |
Correction on sidelink power class capability indication |
Xiaomi |
| R2-2208838 |
Correction on sidelink power class capability indication |
Xiaomi |
| R2-2208839 |
Summary of offline-503 discussion |
Xiaomi |
| R2-2208860 |
Clarification of NULL security algorithm |
ZTE, Samsung, vivo |
| R2-2208862 |
Correction on sidelink capability |
Xiaomi |
| R2-2208863 |
Correction on sidelink capability |
Xiaomi |
| R2-2208864 |
Correction on Missing UE behavior on sidelink reset |
vivo |
| R2-2208870 |
Correction on Missing UE behavior on sidelink reset |
vivo |
| R2-2208902 |
Correction on sidelink power class capability indication |
Xiaomi |
| R2-2208903 |
Correction on sidelink power class capability indication |
Xiaomi |
| R2-2209266 |
Correction on sidelink capability |
Xiaomi |
| 5.2.3 |
User plane corrections |
|
| R2-2207659 |
CR on SL MAC CE handling |
vivo |
| R2-2207660 |
CR on SL MAC CE handling |
vivo |
| R2-2207661 |
Correction on SL LCP restriction for sl-HARQ-FeedbackEnabled |
vivo |
| R2-2207662 |
Correction on SL LCP restriction for sl-HARQ-FeedbackEnabled |
vivo |
| R2-2207663 |
Discussion on the Buffer Size field in the Sidelink BSR formats |
vivo |
| R2-2207664 |
Clarification on the Buffer Size field in the Sidelink BSR formats (Option 1) |
vivo |
| R2-2207665 |
Clarification on the Buffer Size field in the Sidelink BSR formats (Option 1) |
vivo |
| R2-2207666 |
Clarification on the Buffer Size field in the Sidelink BSR formats (Option 2) |
vivo |
| R2-2207667 |
Clarification on the Buffer Size field in the Sidelink BSR formats (Option 2) |
vivo |
| R2-2208047 |
Clarification on UE handling when performing operations on multiple RPs |
Huawei, HiSilicon |
| R2-2208048 |
Clarification on UE handling when performing operations on multiple RPs |
Huawei, HiSilicon |
| R2-2208352 |
Discussion on UL skipping and SL BSR |
ASUSTeK |
| R2-2208353 |
Corrections on UL skipping and SL BSR |
ASUSTeK |
| R2-2208354 |
Corrections on UL skipping and SL BSR |
ASUSTeK |
| R2-2208840 |
Clarification on the Buffer Size field in the Sidelink BSR formats |
vivo |
| R2-2208841 |
Clarification on the Buffer Size field in the Sidelink BSR formats |
vivo |
| R2-2208842 |
Correction on the SL LCP restriction for sl-HARQ-FeedbackEnabled |
vivo |
| R2-2208843 |
Correction on the SL LCP restriction for sl-HARQ-FeedbackEnabled |
vivo |
| R2-2208844 |
Summary of [AT119-e][504][V2X/SL] 38.321 corrections (vivo) |
vivo |
| 5.3.1 |
General and Stage 2 corrections |
|
| R2-2207108 |
Correction on the description of deferred MT-LR |
CATT |
| R2-2207109 |
Correction on the description of deferred MT-LR |
CATT |
| R2-2209208 |
LS to RAN1 on TP to TR 37.985 |
RAN2 |
| 5.3.2 |
RRC corrections |
|
| R2-2207408 |
Change request about Periodicity in SRSp configuration |
vivo |
| R2-2207561 |
Change request about Periodicity in SRSp configuration |
vivo |
| R2-2207873 |
Correction for SRS-PeriodicityAndOffset-R16 |
Huawei, HiSilicon |
| R2-2207874 |
Correction for SRS-PeriodicityAndOffset-R17 |
Huawei, HiSilicon |
| R2-2207875 |
Correction for the capability of SRS-PeriodicityAndOffset-R16 |
Huawei, HiSilicon |
| R2-2207876 |
Correction for the capability of SRS-PeriodicityAndOffset-R17 |
Huawei, HiSilicon |
| R2-2208820 |
[Offline-406][POS] Rel-15 16 positioning RRC (Huawei) |
Huawei, HiSilicon |
| R2-2208821 |
Correction for SRS-PeriodicityAndOffset |
Huawei, HiSilicon |
| R2-2208822 |
Correction for SRS-PeriodicityAndOffset |
Huawei, HiSilicon |
| R2-2208823 |
Correction for the capability of SRS-PeriodicityAndOffset |
Huawei, HiSilicon |
| R2-2208824 |
Correction for the capability of SRS-PeriodicityAndOffset |
Huawei, HiSilicon |
| 5.3.3 |
LPP corrections |
|
| R2-2207103 |
Minor corrections on TS 37.355 |
CATT |
| R2-2207104 |
Minor corrections on TS 37.355 |
CATT |
| R2-2207870 |
Correction to need code in posSIB_R17 |
Huawei, HiSilicon |
| R2-2207871 |
Correction to need code in posSIB_R16 |
Huawei, HiSilicon |
| R2-2207872 |
Correction to need code in posSIB_R15 |
Huawei, HiSilicon |
| R2-2208069 |
Correction of TRP beam information field descriptions for UEB DL-AoD |
Ericsson |
| R2-2208070 |
Clarification on NR-DL-PRS-ResourcesCapability |
Ericsson |
| R2-2208071 |
Clarification on NR-DL-PRS-ResourcesCapability |
Ericsson |
| R2-2208119 |
Issues with DL-PRS Search Window Definitions |
Qualcomm Incorporated |
| R2-2208121 |
Correction to DL-PRS Search Window calculation |
Qualcomm Incorporated |
| R2-2208123 |
Correction to DL-PRS Search Window calculation |
Qualcomm Incorporated |
| R2-2208962 |
Summary of [AT119-e][407][POS] Rel-15/16 LPP (Qualcomm) |
Qualcomm Incorporated |
| 5.4.3 |
RRC corrections |
|
| R2-2207527 |
Corrections to SON/MDT capabilities |
Lenovo |
| R2-2207528 |
Corrections to SON/MDT capabilities |
Lenovo |
| R2-2207942 |
Discussion on UE behaviours of delay measurements upon MO updates |
Huawei, HiSilicon |
| R2-2207943 |
CR on UE behaviours of delay measurements upon MO updates |
Huawei, HiSilicon |
| R2-2207944 |
CR on UE behaviours of delay measurements upon MO updates |
Huawei, HiSilicon |
| R2-2208169 |
On DAPS handover failure handling |
Ericsson |
| R2-2208170 |
On RLF cause determination when RLF occurs due to T312 expiry |
Ericsson |
| R2-2208171 |
On RLF cause determination when RLF occurs due to T312 expiry |
Ericsson |
| R2-2208172 |
On ObtainCommonLocation related configuration |
Ericsson |
| R2-2208173 |
On ObtainCommonLocation related configuration |
Ericsson |
| R2-2208174 |
On including SSB and CSI-RS measurements in RLF report |
Ericsson |
| R2-2208175 |
On including SSB and CSI-RS measurements in RLF report |
Ericsson |
| R2-2208373 |
Discrepancy on inclusion of reconnectCellId |
Samsung Electronics Co., Ltd |
| 6.0.1 |
RRC |
|
| R2-2207002 |
Corrections to initiation upon reception of RAN paging and T380 Expiry |
Samsung Electronics Co., Ltd |
| R2-2207006 |
MsgA PUSCH resource release upon T304 expiry for SCG |
Samsung Electronics Co., Ltd |
| R2-2207013 |
Corrections to MBS paging monitoring during the SDT procedure |
Samsung Electronics Co., Ltd |
| R2-2207267 |
Unified TCI state with deactivated SCG |
Nokia, Nokia Shanghai Bell |
| R2-2207776 |
UE handling of cell-specific parameters provided in dedicated signalling |
Huawei, HiSilicon |
| R2-2208141 |
Miscellaneous non-controversial corrections Set XV |
Ericsson |
| R2-2208654 |
Correction on UERadioPagingInformation and UERadioPagingInfo container |
Ericsson |
| R2-2208937 |
[AT118-e][013][NR17] RRC I (Ericsson) |
Ericsson |
| R2-2208983 |
MsgA PUSCH resource release upon T304 expiry for SCG |
Samsung |
| R2-2208984 |
Corrections for unified TCI state indication in HO |
Nokia, Nokia Shanghai Bell |
| R2-2209144 |
Miscellaneous non-controversial corrections Set XV |
Ericsson (Rapporteur), Lenovo |
| 6.0.2 |
UE capabilities |
|
| R2-2206957 |
LS on Rel-17 RAN4 UE feature list for NR (R4-2211190; contact: CMCC) |
RAN4 |
| R2-2206971 |
LS on updated Rel-17 RAN1 UE features list for NR (R1-2205609; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2207276 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) |
Intel Corporation |
| R2-2207277 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) |
Intel Corporation |
| R2-2207849 |
Editorial corrections on UE capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2207962 |
Capturing one shot large UL timing adjustment |
Nokia, Nokia Shanghai Bell |
| R2-2207971 |
Corrections to UE capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2207972 |
Corrections on UE capabilities |
Nokia, Nokia Shanghai Bell |
| R2-2208507 |
Discussion on positioning SRS transmission capability |
Huawei, HiSilicon |
| R2-2208508 |
Correction on positioning SRS transmission capability |
Huawei, HiSilicon |
| R2-2208509 |
Correction on positioning SRS transmission capability |
Huawei, HiSilicon |
| R2-2208955 |
LS on Rx beam sweeping factor for RRM measurements (R4-2214215; contact: LGE) |
RAN4 |
| R2-2208956 |
LS on Rel-17 RAN4 UE feature list for NR (R4-2214217; contact: CMCC) |
RAN4 |
| R2-2209061 |
Correction on positioning SRS transmission capability |
Huawei, HiSilicon |
| R2-2209072 |
Report of [AT119-e][014][NR17] UE Caps Main (Intel) |
Intel Corporation |
| R2-2209073 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) |
Intel Corporation |
| R2-2209074 |
Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) |
Intel Corporation |
| R2-2209117 |
LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#110 Thursday (R1-2207925; contact: NTT DCOMO, AT&T) |
RAN1 |
| R2-2209137 |
Correction to additionalSpectrumEmission for UL CA in n77 for the US |
Ericsson, Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R2-2209138 |
Correction to additionalSpectrumEmission for UL CA in n77 for the US |
Ericsson, Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R2-2209139 |
Correction to additionalSpectrumEmission for UL CA in n77 for Canada |
Ericsson, Nokia, Nokia Shanghai Bell, T-Mobile USA |
| R2-2209141 |
Ensuring consistent support of capability bits and associated NS-values in n77 in USA |
Ericsson |
| R2-2209142 |
Ensuring consistent support of capability bits and associated NS-values in n77 in USA |
Ericsson |
| R2-2209143 |
Ensuring consistent support of capability bits and associated NS-values in n77 in USA and Canada |
Ericsson |
| R2-2209173 |
LS on Rel-17 RAN4 UE feature list for NR (R4-2215144; contact: CMCC) |
RAN4 |
| R2-2209273 |
Ensuring consistent support of capability bits and associated NS-values in n77 in USA |
Ericsson |
| R2-2209274 |
Ensuring consistent support of capability bits and associated NS-values in n77 in USA and Canada |
Ericsson |
| 6.0.3 |
User Plane related aspects |
|
| R2-2206949 |
LS reply on coordination of R17 gap features (R4-2210624; contact: MediaTek) |
RAN4 |
| R2-2207040 |
Correction to SR transmission with overlapping PUSCH |
Qualcomm Incorporated |
| 6.0.4 |
Other |
|
| R2-2207147 |
Discussion on gaps coordination |
Huawei, HiSilicon |
| R2-2207235 |
Leftover Issues for Gap Coordination |
OPPO |
| R2-2207236 |
Corrections on Gap Activation Limitation |
OPPO |
| R2-2208472 |
Discussion on BWP operation without BW restrictions (FG6-1a) |
MediaTek Inc. |
| R2-2208497 |
Discussion on Gap Coordination |
MediaTek Inc. |
| R2-2208623 |
Gaps coordination |
Ericsson |
| R2-2208961 |
Miscellaneous Corrections |
Nokia (Rapporteur), Huawei |
| R2-2209029 |
Report of [AT119-e][015][NR17] Gap Coordination (MediaTek) |
MediaTek |
| R2-2209091 |
Clarification on Joint Gap Configuration |
MediaTek Inc. |
| R2-2209149 |
LS on BWP operation without restriction (R1-2208168; contact: Qualcomm) |
RAN1 |
| R2-2209270 |
Miscellaneous Corrections |
Nokia (Rapporteur), Huawei |
| 6.1.1 |
Organizational and Stage-2 |
|
| R2-2206910 |
Reply LS on HARQ process for MCCH and Broadcast MTCH(s) (R1-2205215; contact: BBC) |
RAN1 |
| R2-2206912 |
LS on TCI indication in multicast DCI (R1-2205369; contact: CMCC) |
RAN1 |
| R2-2206977 |
Reply LS on the MBS broadcast service continuity and MBS session identification (S4-220827; contact: Qualcomm) |
SA4 |
| R2-2207031 |
Miscellaneous corrections to TS 38.300 on NR MBS |
CATT |
| R2-2207036 |
38.304 Corrections for MBS |
CATT, Nokia, Huawei, HiSilicon, CBN |
| R2-2207038 |
Response to SA4 LS for MBS user service parameters |
Samsung |
| R2-2207222 |
Correction on MBS Interest Indication |
vivo |
| R2-2207223 |
Correction on Layer 2 Architecture for Broadcast |
vivo |
| R2-2207590 |
Rapporteur corrections on RRC |
Huawei, CATT, HiSilicon |
| R2-2207813 |
Miscellaneous corrections for MBS 38.323 |
Xiaomi |
| R2-2208086 |
Clarification of group paging |
Ericsson |
| R2-2208181 |
Stage2 corrections for NR MBS |
Nokia, Nokia Shanghai Bell |
| R2-2208437 |
Corrections on MBS |
CMCC, Huawei |
| R2-2208635 |
Discussion about SA4 LS on USD content with draft LS back |
ZTE, Sanechips |
| R2-2208875 |
Corrections for MBS 38.323 |
Xiaomi |
| R2-2208876 |
Corrections on MBS |
CMCC, Huawei |
| R2-2208884 |
[Offline 605] discussion report: Reply LS to SA4 |
Qualcomm Incorporated |
| R2-2208885 |
Reply LS on the MBS broadcast service continuity and MBS session identification |
RAN2 |
| R2-2209122 |
Reply LS on rate matching patterns and CORESET configuration for MBS (R1-2208072; contact: Huawei) |
RAN1 |
| R2-2209145 |
Corrections on MBS |
CMCC, Huawei |
| R2-2209189 |
Response LS on further outstanding issues in TS 23.247 (S2-2207389; contact: Huawei) |
SA2 |
| R2-2209190 |
LS on AS-NAS layer interactions for MBS (S2-2207409; contact: Huawei) |
SA2 |
| R2-2209198 |
LS on response to LS on parameters preconfigured in the UE to receive MBS service (S2-2207888; contact: Huawei) |
SA2 |
| R2-2209201 |
Reply LS on AS-NAS layer interactions for MBS (C1-225249; contact: Huawei) |
CT1 |
| 6.1.2 |
RRC corrections |
|
| R2-2207032 |
Corrections related to MBS Interest Indication |
CATT |
| R2-2207033 |
Corrections on Broadcast Configuration |
CATT, CBN |
| R2-2207034 |
Corrections on multicast MRB handling |
CATT |
| R2-2207035 |
Miscellaneous Corrections to TS 38.331 |
CATT |
| R2-2207039 |
RRC Corrections for MBS |
Samsung |
| R2-2207225 |
Clarification on LCH Reassociation |
vivo |
| R2-2207555 |
TMGI handling |
Nokia, Nokia Shanghai Bell |
| R2-2207591 |
Clarfication on the early configuration of MBS broadcast search space |
Huawei, CBN, HiSilicon |
| R2-2207592 |
Discussion on decoding of the TMGI in MII |
Huawei, CBN, HiSilicon |
| R2-2208084 |
Broadcast sessions with the same MRB configuration |
Ericsson |
| R2-2208088 |
MII signalling when SIB21 is absent |
Ericsson |
| R2-2208095 |
Multicast-specific PUCCH-Config when multicast feedback is not configured with a priority value |
Qualcomm Incorporated |
| R2-2208589 |
Counter Check Procedure for Multicast |
Samsung |
| R2-2208639 |
Miscellaneous CR to TS 38.331 on NR MBS |
ZTE, Sanechips |
| R2-2208810 |
LS on support of positioning in FR2-2 |
RAN2 |
| R2-2208871 |
[Pre119-e][601][MBS-R17] Summary of A.I. 6.1.2 / RRC corrections (Huawei) |
Huawei, HiSilicon |
| R2-2208874 |
Rapporteur corrections on RRC |
Huawei, CATT, HiSilicon |
| R2-2208881 |
[AT119-e][601][MBS-R17] RRC corrections |
Huawei, HiSilicon |
| R2-2209094 |
MBS corrections for RRC |
Huawei, CATT, HiSilicon |
| 6.1.3 |
Other CP corrections |
|
| R2-2207224 |
Clarification on Group Paging for Inactive UE |
vivo |
| R2-2207554 |
MBS prioritization with slice based reselection |
Nokia, Nokia Shanghai Bell |
| R2-2207562 |
Discussion on the maximum G-RNTI for MBS |
MediaTek inc. |
| R2-2207563 |
Discussion and correction on UE capabilities for MBS |
MediaTek inc. |
| R2-2207564 |
Corrections on the maximum G-RNTI for MBS |
MediaTek inc. |
| R2-2207811 |
Simultaneous PDSCH processing capability for MBS |
Xiaomi |
| R2-2207814 |
Correction on the G-RNTI and G-CS-RNTI configuration |
Xiaomi |
| R2-2208085 |
Clarification of frequency prioritization for MBS broadcast |
Ericsson |
| R2-2208087 |
MBS and RedCap |
Ericsson |
| R2-2208500 |
Remaining MBS UE capability open issues |
Intel Corporation |
| R2-2208636 |
On supported max number of G-RNTI for MBS broadcast |
ZTE, Sanechips |
| R2-2208872 |
Summary of Rel-17 MBS 6.1.3 Other CP corrections |
MediaTek Inc. (Moderator) |
| R2-2208877 |
38.304 Corrections for MBS |
CATT, Nokia, Huawei, HiSilicon, CBN |
| R2-2208879 |
Draft 38.306 CR for MBS UE capability corrections |
MediaTek Inc. |
| R2-2208880 |
Draft 38.331 CR for MBS UE capability corrections |
MediaTek Inc. |
| R2-2208882 |
Summary of [AT119-e][602] Rel-17 MBS CP Other CP corrections |
MediaTek Inc. (Moderator) |
| R2-2209146 |
Draft 38.331 CR for MBS UE capability corrections |
MediaTek Inc. |
| R2-2209147 |
Draft 38.306 CR for MBS UE capability corrections |
MediaTek Inc. |
| R2-2209268 |
38.304 Corrections for MBS |
CATT, Nokia, Huawei, HiSilicon, CBN |
| 6.1.4 |
MAC corrections |
|
| R2-2207046 |
MAC Corrections for MBS |
Samsung |
| R2-2207226 |
Clarification on pdsch-AggregationFactor in NR MBS |
vivo |
| R2-2207470 |
38.321 CR Correction on the HARQ buffer flush for the MBS broadcast |
Beijing Xiaomi Software Tech |
| R2-2207593 |
Clarification on retransmission and RTT timer maintenance |
Huawei, HiSilicon |
| R2-2207594 |
Further consideration on inactivity timers for unicast and multicast |
Huawei, HiSilicon |
| R2-2207812 |
HARQ process for MCCH and Broadcast MTCH(s) |
Xiaomi |
| R2-2208637 |
Miscellaneous CR to TS 38.321 on NR MBS |
ZTE, Sanechips |
| R2-2208873 |
[Pre119-e][603][MBS-R17] Summary of A.I. 6.1.4 and 6.1.5 / UP corrections (Lenovo) |
Lenovo |
| R2-2208878 |
38.321 corrections for MBS |
OPPO |
| R2-2208883 |
Summary of [AT119-e][603][MBS-R17] UP corrections (Lenovo) |
Lenovo |
| R2-2209269 |
38.321 corrections for MBS |
OPPO |
| 6.1.5 |
Other UP Corrections |
|
| R2-2207370 |
PDCP related corrections for MBS |
Nokia, Nokia Shanghai Bell |
| R2-2207565 |
PDCP corrections for MBS |
MediaTek inc. |
| R2-2207595 |
PDCP state variables handling during multicast MRB suspend |
Huawei, Xiaomi, CBN, HiSilicon |
| R2-2207692 |
Misalignment between RRC and PDCP specs regarding multicastHFN-AndRefSN |
Lenovo |
| R2-2208590 |
Correction for Initial value of RX_DELIV for Multicast |
Samsung |
| R2-2208638 |
Miscellaneous CR to TS 38.323 on NR MBS |
ZTE, Sanechips |
| 6.2.1 |
Organizational and Stage-2 corrections |
|
| R2-2207319 |
Rel-17 Stage-2 CPAC corrections |
Nokia, Nokia Shanghai Bell |
| R2-2207727 |
Introduction of signaling flows for CHO+MR-DC |
Ericsson |
| R2-2207741 |
Correction on CHO with MR-DC in TS 37.340 |
vivo |
| R2-2208404 |
Corrections for DCCA enhancement |
ZTE Corporation (Rapporteur), Sanechips, Samsung |
| R2-2208644 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon |
| R2-2208645 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon |
| R2-2208646 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon |
| R2-2208695 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon |
| R2-2208696 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon |
| R2-2208713 |
Report of [AT119-e][220][DCCA] Stage-2 corrections to DCCA (ZTE) |
ZTE |
| R2-2208714 |
Corrections for DCCA enhancement |
ZTE Corporation (Rapporteur), Sanechips, Samsung |
| R2-2208941 |
Corrections for DCCA enhancement |
ZTE Corporation (Rapporteur), Sanechips, Samsung, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| 6.2.2.1 |
MAC PDCP corrections |
|
| R2-2207011 |
MIscellaneous Corrections for SCG activation_deactivation |
Samsung Electronics Co., Ltd |
| R2-2207393 |
Discussion on MAC and PDCP Aspects |
CATT |
| R2-2207541 |
Clarification on BFD while PSCell is deactivated |
Nokia, Nokia Shanghai Bell |
| R2-2207852 |
Correction of BFD procedure for deactivated PSCell |
Sharp |
| R2-2207853 |
CR related to BFD mechanism for deactivated PSCell |
Sharp |
| R2-2207854 |
Remaining issues for BWP operation in deactivated SCG |
Sharp |
| R2-2207855 |
CR on 38.321 for Remaining issues for BWP handling in deactivated SCG |
Sharp |
| R2-2207966 |
[E129] Stop/resume BFD at beam failure for deactivated SCG |
Ericsson |
| R2-2208465 |
Correction for activation/deactivation of SCells |
Xiaomi |
| R2-2208650 |
Correction on SCG deactivation |
Huawei, HiSilicon |
| R2-2208697 |
Correction on SCG deactivation |
Huawei, HiSilicon |
| R2-2208718 |
Report of [AT119-e][222][DCCA] MAC/PDCP corrections to DCCA (Nokia) |
Nokia |
| R2-2208719 |
Clarification on BFD while PSCell is deactivated |
Nokia, Nokia Shanghai Bell |
| R2-2209236 |
Clarification on BFD while PSCell is deactivated |
Nokia, Nokia Shanghai Bell |
| R2-2209253 |
Corrections to MAC regarding deactivated SCG |
Nokia, Nokia Shanghai Bell, Samsung Electronics, Ericsson |
| 6.2.2.2 |
RRC corrections |
|
| R2-2207305 |
BFD with two BFD-RS sets on deactivated SCG |
Ericsson |
| R2-2207306 |
[E131] Handling of UAI for deactivated SCG |
Ericsson |
| R2-2207394 |
Corrections on scg-State |
CATT |
| R2-2207395 |
Discussion on RRC Aspects for SCG Activation and Deactivation |
CATT |
| R2-2208286 |
UAI transmission in SCG deactivation |
Sharp |
| R2-2208405 |
CR on SCG failure type |
ZTE Corporation, Sanechips |
| R2-2208648 |
SCG state in the MCG fast recovery |
Huawei, HiSilicon |
| R2-2208651 |
UE assistance information while the SCG is deactivated |
Huawei, HiSilicon |
| R2-2208715 |
Report of [AT119-e][221][DCCA] RRC corrections to SCG deactivation (Huawei) |
Huawei |
| R2-2208716 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon |
| R2-2208717 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon |
| R2-2209244 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon, Ericsson |
| R2-2209245 |
Corrections for further MR-DC enhancements |
Huawei, HiSilicon, Ericsson |
| 6.2.3.1 |
Corrections to CPAC network aspects |
|
| R2-2207320 |
Rel-17 CPAC corrections to NR 38.331 |
Nokia, Nokia Shanghai Bell |
| R2-2207321 |
On SN-MN awareness of conditional reconfiguration's validity or execution |
Nokia, Nokia Shanghai Bell |
| R2-2207494 |
Clarifications on prepared PSCell addition by candidate SN |
NEC |
| R2-2207495 |
Clarifications on prepared PSCell addition by candidate SN in CPC |
NEC |
| R2-2207636 |
On co-existence of MN and SN initiated conditional reconfiguration |
Lenovo, ZTE Corporation, Sanechips, CATT |
| R2-2207639 |
On maximum number of SN initiated conditional reconfigurations |
Lenovo, ZTE Corporation, Sanechips, CATT |
| R2-2207728 |
Outstanding issue for CPC |
Ericsson |
| R2-2207740 |
Discussion on release of conditional configuration |
vivo |
| R2-2208720 |
Report of [AT119-e][223][DCCA] RRC corrections to CPAC (Ericsson) |
Ericsson |
| R2-2208721 |
Corrections for further CPAC |
Ericsson |
| R2-2208722 |
Corrections for further CPAC |
Ericsson |
| 6.2.3.2 |
Corrections to CPAC UE signalling |
|
| R2-2207396 |
Discussion on Conditional Reconfiguration for CPAC and CHO |
CATT |
| R2-2207397 |
Discussion on CHO with SCG |
CATT |
| R2-2207462 |
Discussion on handling of simultaneous configuration of R16 and R17 CPC |
Apple |
| R2-2207463 |
CR for handling R16 CPC with R17 CPA/CPC |
Apple |
| R2-2208406 |
Discussion on conditional reconfiguration release |
ZTE Corporation, Sanechips |
| R2-2208407 |
CR on conditional reconfiguration release |
ZTE Corporation, Sanechips |
| R2-2208408 |
CR on conditional reconfiguration release |
ZTE Corporation, Sanechips |
| R2-2208647 |
[Post118-e][227][DCCA] Resolving E022 and E023 for CPAC (Huawei) |
Huawei, HiSilicon |
| R2-2208649 |
Triggering of multiple cells for conditional reconfiguration execution |
Huawei, HiSilicon |
| 6.2.4 |
Temporary RS for SCell activation |
|
| R2-2207542 |
Corrections MAC regarding TRS activation |
Nokia, Nokia Shanghai Bell |
| R2-2207788 |
Correction to TRS for fast SCell activation |
vivo |
| 6.3.1 |
Organizational |
|
| R2-2208000 |
Correction on MUSIM related changes |
Nokia, Nokia Shanghai Bell |
| R2-2208033 |
Update to gap handling for Multi-USIM (38.300) |
Ericsson |
| R2-2208461 |
Correction of NR RRC support for MUSIM |
vivo |
| R2-2209185 |
Reply LS on NAS busy indication in RRC_INACTIVE (S2-2207029; contact: Samsung) |
SA2 |
| 6.3.3 |
NW switching for multi-SIM with or without leaving RRC_CONNECTED |
|
| R2-2207164 |
CR on the Gap Numbers Restriction |
ZTE Corporation, Sanechips |
| R2-2207165 |
CR on the MUSIM-GapInfo |
ZTE Corporation, Sanechips |
| R2-2207166 |
Further Clarification on the Waiting Timer for Leaving Connected State |
ZTE Corporation, Sanechips |
| R2-2207231 |
Corrections on NW Switching for Multi-SIM with or without Leaving RRC_CONNECTED_38.300 |
OPPO |
| R2-2207232 |
Corrections on NW Switching for Multi-SIM with or without Leaving RRC_CONNECTED_38.331 |
OPPO |
| R2-2207238 |
Corrections on Capability for MUSIM UE |
OPPO |
| R2-2207505 |
Discussion on handling of aperiodic MUSIM gap |
Huawei, HiSilicon |
| R2-2207670 |
Support eDRX in Multi-SIM scenario |
Spreadtrum Communications |
| R2-2207958 |
Corrections to MUSIM gaps |
Huawei, HiSilicon |
| R2-2207961 |
Discussion on the MUSIM gap release during RRC reestablishment |
Huawei, HiSilicon |
| R2-2207987 |
Applicability of otherConfig MUSIM IEs for SRB3 |
Nokia, Nokia Shanghai Bell |
| R2-2207994 |
Clarification for MUSIM Assistance Information in DC for reconfiguration with Sync |
Nokia, Nokia Shanghai Bell |
| R2-2208029 |
Correction to musim-GapLength |
Ericsson |
| R2-2208030 |
Mac updates for MUSIM |
Ericsson |
| R2-2208032 |
Discussion on gap length IE optionality |
Ericsson |
| R2-2208035 |
On Remaining Issues ofr MUSIM Switching Procedures |
Nokia, Nokia Shanghai Bell |
| R2-2208344 |
Clarification on performing MUSIM gap configuration procedure |
Samsung Electronics Co., Ltd |
| R2-2208369 |
Further discussion on re-establishment handling while T346g timer is running |
Samsung Electronics Co., Ltd |
| R2-2208462 |
corrections on RACH procedure during MUSIM gaps |
vivo |
| R2-2208470 |
UE MAC operations during MUSIM gaps |
Samsung R&D Institute India |
| R2-2208496 |
Correction on MUSIM gap configuration |
MediaTek Inc. |
| R2-2208683 |
On Remaining Issues ofr MUSIM Switching Procedures |
Nokia, Nokia Shanghai Bell |
| R2-2208723 |
Report of [AT119-e][230][MUSIM] Stage-2 and MAC corrections to MUSIM (Samsung) |
Samsung |
| R2-2208724 |
Stage-2 corrections on MUSIM |
Samsung |
| R2-2208725 |
MAC corrections on MUSIM |
Samsung |
| R2-2208726 |
Report of [AT119-e][231][MUSIM] RRC corrections to MUSIM (vivo) |
vivo |
| R2-2208727 |
Correction of NR RRC support for MUSIM |
vivo |
| R2-2208728 |
Report of [AT119-e][232][MUSIM] Potential clarifications to MUSIM (Ericsson) |
Ericsson |
| R2-2209214 |
Miscellaneous correction of NR RRC support for MUSIM |
vivo |
| 6.4.1 |
Organizational and Stage-2 |
|
| R2-2207784 |
Corrections on the terminology of F1-terminating IAB-donor |
Huawei, HiSilicon |
| R2-2208463 |
Miscilaneous Corrections to 37340 |
vivo |
| R2-2208604 |
Removing F1-termination node in F1-C transfer procedure |
Samsung Electronics Romania |
| R2-2208643 |
Corrections on F1-C transfer |
Nokia, Nokia Shanghai Bell |
| R2-2209088 |
Report of [AT119-e][016][eIAB] Stage-2 (vivo) |
vivo (Rapporteur) |
| R2-2209089 |
Miscellaneous Corrections to 37.340 |
vivo (Rapporteur) |
| 6.4.2 |
Control Plane |
|
| R2-2206929 |
LS on upper layers parameters for Rel-17 eIAB (R1-2205644; contact: AT&T) |
RAN1 |
| R2-2206935 |
LS on range of power control parameters for eIAB (R4-2210642; contact: Samsung) |
RAN4 |
| R2-2207190 |
Correction on the release of BAP config |
ZTE, Sanechips |
| R2-2207783 |
Corrections on availabilityCombinations and IAB-ResourceConfig for eIAB |
Huawei, HiSilicon |
| R2-2208101 |
Rapporteur Miscellaneous RRC Corrections |
Ericsson |
| R2-2208642 |
Corrections to the AI index configuration |
Ericsson |
| R2-2209077 |
Summary of [AT119-e][017][IAB17] Control Plane |
Ericsson |
| R2-2209078 |
Rapporteur Miscellaneous RRC Corrections for eIAB |
Ericsson |
| 6.4.3 |
User Plane |
|
| R2-2207188 |
Corrections on IAB related MAC CEs |
ZTE, Sanechips |
| R2-2207189 |
Miscellaneous corrections on IAB in TS38.340 |
ZTE, Sanechips |
| R2-2207402 |
Support SCG deactivation for IAB nodes and other miscellaneous corrections |
Fujitsu |
| R2-2207625 |
Miscellaneous corrections to 38.321 on Integrated Access and Backhaul for NR Rel-17 |
Samsung R&D Institute UK |
| R2-2207781 |
Miscellaneous corrections in TS 38.340 for eIAB |
Huawei, HiSilicon |
| R2-2207782 |
Corrections on the Desired Guard Symbol query and extended pre-BSR |
Huawei, HiSilicon |
| R2-2208100 |
Corrections to multiplexing mode info definition |
Ericsson |
| R2-2208102 |
Miscellaneous MAC Corrections |
Ericsson |
| R2-2208907 |
Proposal for handling of submissions to AI 6.4.3 - eIAB MAC corrections (Samsung) |
Samsung |
| R2-2208957 |
Report of [AT119-e][019][IAB17] BAP |
Huawei, HiSilicon |
| R2-2208958 |
Miscellaneous corrections in TS 38.340 for eIAB |
Huawei, HiSilicon |
| R2-2208965 |
Summary of discussion [AT119-e][018][IAB17] MAC (Samsung) |
Samsung (rapporteur) |
| R2-2208966 |
Miscellaneous corrections to 38.321 on Integrated Access and Backhaul for NR Rel-17 |
Samsung, Huawei |
| 6.5.1 |
Organizational |
|
| R2-2206922 |
LS on Rel-17 URLLC/IIoT RRC parameter updates (R1-2205507; contact: Nokia) |
RAN1 |
| R2-2208012 |
Clarification on PUCCH cell switching for TDD cells |
Nokia, Nokia Shanghai Bell, Ericsson, Qualcomm, Samsung, ZTE Corporation |
| 6.5.2 |
Control Plane |
|
| R2-2208060 |
Correction to the field description of usage-pdc |
Huawei, HiSilicon |
| R2-2208556 |
CR on 38.331 of field description in PUCCH-Config for PUCCH Carrier Switch |
ZTE Corporation, Sanechips, Nokia, Nokia Shanghai Bell, Ericsson, Samsung, Qualcomm |
| 6.5.3 |
User Plane |
|
| R2-2207432 |
Discussion on MAC layer operation at PUSCH cancellation |
Apple |
| R2-2207433 |
Draft CR for MAC layer operation at PUSCH cancellation |
Apple, Ericsson |
| R2-2207506 |
Consideration on CG-PUSCH cancellation for UCI -only case |
CATT |
| R2-2207507 |
Simultaneous transmission of SR and PUSCH over different PUCCH groups |
CATT |
| R2-2207792 |
Clarification on SR and PUSCH collision-Alt1 |
OPPO, Samsung |
| R2-2207793 |
Clarification on SR and PUSCH collision-Alt2 |
OPPO, Samsung |
| R2-2207794 |
Clarification on SR and PUSCH collision-Alt2 |
OPPO, Samsung |
| R2-2207795 |
Clarification on SR and PUSCH collision-Alt2 |
OPPO, Samsung |
| R2-2207796 |
Issue on a CG transmission cancelled by a DG without UL-SCH |
OPPO |
| R2-2208013 |
MAC impact on PHY prioritization |
Nokia, Nokia Shanghai Bell |
| R2-2208014 |
Correction on TB generated for UCI multiplexing |
Nokia, Nokia Shanghai Bell |
| R2-2208061 |
Discussion on deprioritized CG-PUSCH with UCI only TB |
Huawei, HiSilicon |
| R2-2208062 |
Discussion on simultaneous transmissions of SR and PUSCH |
Huawei, HiSilicon |
| R2-2208122 |
Open Issues in IIOT UP |
Qualcomm Incorporated |
| R2-2208355 |
Discussion on SR error handling on PUCCH Cells |
ASUSTeK |
| R2-2208588 |
Correction for De-prioritizatin of Overlapping Resources |
Samsung |
| R2-2208926 |
Summary of User Plane Issues in IIOT/URLLC |
Samsung |
| R2-2208975 |
Correction for Simultaneous Transmission of SR and PUSCH |
OPPO, Samsung |
| R2-2208976 |
Correction for Simultaneous Transmission of SR and PUSCH UE Capability |
OPPO |
| R2-2209005 |
Offline 306: User Plane Issues in IIOT/URLLC |
Samsung |
| R2-2209006 |
Correction for Simultaneous Transmission of SR and UL-SCH |
Samsung, OPPO, Huawei, HiSilicon |
| R2-2209014 |
Correction for Simultaneous Transmission of SR and PUSCH UE Capability |
OPPO |
| 6.6.1 |
Organizational |
|
| R2-2206907 |
Reply LS on Small Data Transmission (C1-224149; contact: Apple) |
CT1 |
| R2-2206931 |
LS on transferring SDT configuration and SRS positioning Inactive configuration from DU to CU (R3-223955; contact: Google) |
RAN3 |
| R2-2206953 |
Reply LS on TA validation for CG-SDT (R4-2211122; contact: ZTE) |
RAN4 |
| R2-2207120 |
Response to RAN3 LS on SDT containers for F1-AP |
Intel Corporation |
| R2-2207900 |
Corrections on SDT |
Nokia, Nokia Shanghai Bell, Samsung |
| R2-2207928 |
Editor's correction to MAC spec for Small Data Transmission |
Huawei, HiSilicon |
| R2-2207976 |
draft reply LS on TA validation for CG-SDT |
ZTE Corporation, Sanechips |
| R2-2208072 |
On transferring SDT configuration and SRS positioning Inactive configuration from DU to CU |
Ericsson |
| R2-2208596 |
Discussion on RRC IEs in the RAN3 specification |
Google Inc. |
| R2-2208911 |
Corrections on SDT |
Nokia, Nokia Shanghai Bell, Samsung |
| R2-2208915 |
Reply LS on transferring SDT configuration and SRS positioning Inactive configuration from DU to CU |
RAN2 |
| R2-2208948 |
Summary of [Post119-e][302][Sdata] UP open issues and CR to 38.321 (Huawei) |
Huawei |
| R2-2208949 |
Change to MAC spec for Small Data Transmission |
Huawei, HiSilicon |
| R2-2208973 |
Report of [AT119-e][311][SDT-Positioning] Config Transfer |
Google |
| R2-2208974 |
[DRAFT] Reply LS on transferring SDT configuration and SRS positioning Inactive configuration from DU to CU |
Google |
| R2-2208990 |
Reply LS on TA validation for CG-SDT |
RAN2 |
| R2-2209013 |
Reply LS on TA validation for CG-SDT |
RAN2 |
| R2-2209125 |
Reply LS on common search space for small data transmission (R1-2208107; contact: ZTE) |
RAN1 |
| 6.6.2 |
User plane common aspects |
|
| R2-2207001 |
cg-SDT-TimeAlignmentTimer Handling |
Samsung Electronics Co., Ltd |
| R2-2207004 |
Issues for RA during CG-SDT procedure |
Samsung Electronics Co., Ltd |
| R2-2207359 |
cg-SDT-TimeAlignmentTimer maintenance during 2-step RA |
Langbo |
| R2-2207360 |
cg-SDT-TimeAlignmentTimer handling for RA-SDT |
Langbo |
| R2-2207416 |
Analysis on remaining issues for SDT |
CATT |
| R2-2207571 |
Correction on SSB selection for CG-SDT |
LG Electronics Inc. |
| R2-2207572 |
CR for correction on SSB selection for CG-SDT |
LG Electronics Inc. |
| R2-2207573 |
Clarification of Bj increment |
LG Electronics Inc. |
| R2-2207815 |
Correction on the stored RSRP for TA validation |
Xiaomi |
| R2-2207901 |
LCH restrictions at SDT mode selection |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, LGE |
| R2-2207902 |
MAC procedure issues |
Nokia, Nokia Shanghai Bell |
| R2-2207906 |
User plane issues for SDT |
NEC |
| R2-2207929 |
Text Proposal for RSRP-based TA validation |
Huawei, HiSilicon |
| R2-2207930 |
TAT maintenance for CG-SDT when receiving TAC MAC CE |
Huawei, Ericsson, HiSilicon, Nokia, Nokia Shanghai Bell, ZTE corporation |
| R2-2208117 |
LCH restrictions for CG-SDT |
Ericsson |
| R2-2208266 |
Correction on CG-SDT Transmission |
vivo |
| R2-2208356 |
Correction on SR delay timer |
ASUSTeK |
| R2-2208660 |
Clarification on uci-onPUSCH for CG-SDT |
vivo |
| R2-2208912 |
Summary of [AT119-e][302][Sdata] UP open issues and CR to 38.321 (Huawei) |
Huawei, HiSilicon |
| 6.6.3 |
Control plane common aspects |
|
| R2-2207003 |
T319a synchronisation issue |
Samsung Electronics Co., Ltd |
| R2-2207417 |
Handling of sdt-Config upon reception of RRCRelease message |
CATT |
| R2-2207418 |
PDCP Re-establishment for SRB(s) upon initiation of SDT |
CATT |
| R2-2207907 |
Issues due to delay of the start of T319a |
NEC |
| R2-2207965 |
UAC for non-SDT initiation during SDT |
Google Inc. |
| R2-2207977 |
RRC corrections for SDT |
ZTE Corporation, Sanechips |
| R2-2207988 |
ROHC continuity and initial BWP related corrections |
Huawei, HiSilicon |
| R2-2208130 |
BWP for CG-SDT |
Ericsson |
| R2-2208218 |
RRC state preference during SDT procedure |
Nokia, Nokia Shanghai Bell |
| R2-2208269 |
Correction on SRB1 Handling in SDT |
vivo |
| R2-2208357 |
Correction on T319a |
ASUSTeK |
| R2-2208640 |
Discussion on UDC continuity in SDT |
China Telecom |
| R2-2208655 |
CR for TS38.300 on Support of UDC in SDT |
China Telecom |
| R2-2208656 |
CR for TS38.331 on Support of UDC in SDT |
China Telecom |
| R2-2208987 |
Report of [AT119-e][301][Sdata] CP Open issues and CR to 38.331 (ZTE) |
ZTE Corporation (rapporteur) |
| R2-2208989 |
RRC corrections for SDT |
ZTE Corporation, Sanechips |
| R2-2209211 |
RRC corrections for SDT |
ZTE Corporation, Sanechips |
| 6.7.1 |
Organizational |
|
| R2-2207020 |
Correction on SRAP for L2 U2N Relay |
OPPO |
| R2-2207021 |
Terminology alignment for Communication and Disocvery |
OPPO |
| R2-2207449 |
Miscellaneous corrections for NR Sidelink Relay (rapporteur CR) |
Apple |
| R2-2208194 |
Miscellaneous corrections on 38.304 for SL relay |
Ericsson (Rapporteur) |
| R2-2208484 |
RRC corrections for sidelink relay |
Huawei, HiSilicon |
| R2-2208798 |
Summary of [AT119-e][417][Relay] Communication and discovery terminology (OPPO) |
OPPO |
| R2-2208799 |
Correction on SRAP for L2 U2N Relay |
OPPO |
| R2-2208812 |
Miscellaneous corrections for NR Sidelink Relay (rapporteur CR) |
Apple |
| R2-2208813 |
RRC corrections for sidelink relay |
Huawei, HiSilicon |
| R2-2208828 |
Report of [AT119-e][414][Relay] Rel-17 relay RRC (Huawei |
Huawei, HiSilicon |
| R2-2208829 |
Summary of User plane corrections |
OPPO |
| R2-2208917 |
Clarifications on UE PC5 capabilities for sidelink Relay |
Qualcomm |
| R2-2209209 |
Correction on SRAP for L2 U2N Relay |
OPPO |
| R2-2209216 |
RRC corrections for sidelink relay |
Huawei, HiSilicon |
| R2-2209217 |
Correction on maxNrofRemoteUE |
Huawei, HiSilicon |
| R2-2209265 |
Miscellaneous corrections for NR Sidelink Relay (rapporteur CR) |
Apple |
| R2-2209275 |
Correction on SRAP for L2 U2N Relay |
OPPO |
| 6.7.2.1 |
Stage 2 corrections |
|
| R2-2207079 |
Correction on miscellaneous issues for NR sidelink relay in 38300 |
OPPO |
| R2-2207201 |
TP to introduce Rel-17 sidelink relay and discovery in TR 37.985 |
ZTE |
| R2-2207203 |
Corrections for path switch in 38.300 |
ZTE |
| R2-2207450 |
Correction on user plane and control plan procedures for U2N relay in Stage 2 |
Apple |
| R2-2207513 |
Corrections on Sidelink Relay |
CATT |
| R2-2208004 |
Miscellaneous corrections on SL Relay specification |
Nokia, Nokia Shanghai Bell |
| R2-2208193 |
Miscellaneous corrections on 38.300 for SL relay |
Ericsson |
| R2-2208485 |
Stage2 clarifications on sidelink relay |
Huawei, HiSilicon |
| R2-2208791 |
Summary of Phase-1 discussion [AT119-e][415][Relay] Rel-17 relay stage 2 |
MediaTek Inc. |
| R2-2208814 |
Correction on stage 2 for sidelink relay |
MediaTek Inc. |
| R2-2208815 |
Draft CR to introduce sidelink relay and discovery |
ZTE, Sanechips, MediaTek Inc. |
| R2-2209025 |
Correction on stage 2 for sidelink relay |
MediaTek Inc., Nokia, Nokia Shanghai Bell |
| R2-2209271 |
Correction on stage 2 for sidelink relay |
MediaTek Inc., Nokia, Nokia Shanghai Bell |
| 6.7.2.2 |
Control plane corrections |
|
| R2-2207018 |
Discussion on left issues for CP |
OPPO |
| R2-2207019 |
Correction for U2N Relay |
OPPO |
| R2-2207176 |
Correction on relay UE mobility handling |
Xiaomi |
| R2-2207177 |
Correction on SI request |
Xiaomi |
| R2-2207178 |
Correction on SIB12 forwarding |
Xiaomi |
| R2-2207179 |
Miscellaneous correction |
Xiaomi |
| R2-2207200 |
Correction on SUI message to differentiate V2X and ProSe service |
ZTE |
| R2-2207202 |
Correction on remote UE’s System Information acquisition |
ZTE |
| R2-2207362 |
Left issues for SUI message |
SHARP Corporation |
| R2-2207451 |
Correction on PC5 RLC channel configuration for L2 U2N relay |
Apple |
| R2-2207452 |
Correction on SUI procedure for L2 remote UE |
Apple |
| R2-2207514 |
Disussion on SRAP entity release |
CATT |
| R2-2207515 |
Miscellaneous Corrections on Sidelink RRC procedures |
CATT |
| R2-2207536 |
Correction on RRC connection suspension of remote UE |
Sharp |
| R2-2207651 |
Correction for notification message with re-establishment |
Lenovo |
| R2-2207763 |
Correction on measurement reporting procedure for L2 U2N Relay |
vivo |
| R2-2207764 |
Miscellaneous corrections on L2 U2N CP procedures |
vivo |
| R2-2208195 |
Clarification on capability filter for sidelink relay |
Ericsson |
| R2-2208196 |
Clarification on SRB3 configuration for sidelink relay |
Ericsson |
| R2-2208197 |
Clarification on the prohibit timer for on-demand SIB for SL relay |
Ericsson |
| R2-2208215 |
Clarifications on UE PC5 capabilities for sidelink Relay |
Nokia, Nokia Shanghai Bell |
| R2-2208255 |
Correction on SidelinkUEInformationNR for SL relay |
Samsung |
| R2-2208256 |
Correction on measurement report of L2 U2N relay UE |
Samsung |
| R2-2208358 |
Clarifications on RRC procedural text for L2 U2N relay operation |
ASUSTeK |
| R2-2208359 |
Correction on PC5-RRC connection release |
ASUSTeK |
| R2-2208360 |
Clarification on radio resource release on L2 U2N Remote UE |
ASUSTeK |
| R2-2208478 |
Correction on rlf-TimersAndConstants |
Google Inc. |
| R2-2208486 |
Clarification on L2 Remote UE threshold conditions for service continuity |
Huawei, HiSilicon |
| R2-2208795 |
[Pre119-e][403] Summary of relay control plane corrections (Huawei) |
Huawei, HiSilicon |
| 6.7.2.3 |
User plane corrections |
|
| R2-2207453 |
Correction on SRAP header handling in L2 Relay UE |
Apple |
| R2-2207516 |
Correction on PDCP for L2 U2N Relay |
CATT |
| R2-2208156 |
Correction to logical channel selection for DRX in sidelink Relay |
Nokia, Nokia Shanghai Bell |
| R2-2208361 |
SRAP data PDU discard examination |
ASUSTeK |
| R2-2208487 |
Discussion on SRAP entity handling |
Huawei, HiSilicon |
| R2-2208826 |
Correction on PDCP for L2 U2N Relay |
CATT, OPPO |
| 6.7.2.4 |
Discovery and re- selection |
|
| R2-2207080 |
Discussion on MAC filtering for reception of discovery message |
OPPO |
| R2-2207654 |
Correction for relay reselection while T300 is running |
Lenovo |
| R2-2207765 |
On the problem for mode-1 dedicated discovery TX pool |
vivo |
| R2-2207766 |
[Draft] LS on mode-1 dedicated discovery transmission pool |
vivo |
| R2-2207967 |
Clarification of SD-RSRP and SL-RSRP in TS 38.331 |
NEC Corporation |
| R2-2208228 |
Support of SL CG for discovery message |
Huawei, HiSilicon |
| R2-2208796 |
Summary of 6.7.2.4 on Discovery and re-selection |
Lenovo |
| R2-2208804 |
[AT119-e][418][Relay] Remaining proposals on discovery and (re)selection (Lenovo) |
Lenovo |
| R2-2208934 |
[AT119-e][418][Relay] Remaining proposals on discovery and (re)selection (Lenovo) |
Lenovo |
| R2-2209207 |
LS on resource pool index in DCI Format 3_0 |
RAN2 |
| 6.8.1 |
Organizational |
|
| R2-2206909 |
Reply LS on Slice list and priority information for cell reselection (C1-224295; contact: OPPO) |
CT1 |
| R2-2207797 |
Discussion on CT1 Reply LS on cell reselection |
OPPO |
| R2-2207951 |
Rapporteur corrections on TS 38.331 for RAN Slicing |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2208001 |
Slicing related stage 2 corrections |
Nokia (rapporteur), Ericsson |
| R2-2208002 |
Slice Group considerations based on CT1 LS (R2-2206909/C1-224295) |
Nokia, Nokia Shanghai Bell |
| R2-2208993 |
Corrections on TS 38.306 for RAN Slicing |
Huawei, HiSilicon |
| R2-2209196 |
LS Out on LS on slice list and priority information for cell reselection and Random Access (S2-2207698; contact: ZTE) |
SA2 |
| 6.8.2 |
Cell reselection |
|
| R2-2207337 |
Correction for cell reselection |
Lenovo |
| R2-2207338 |
CR for Correction for cell reselection |
Lenovo |
| R2-2207678 |
Miscellaneous corrections to slice-specific cell reselection |
Spreadtrum Communications |
| R2-2207818 |
Correction on TS 38.331 for RAN slicing |
CATT |
| R2-2207819 |
Discussion paper on the mapping between slices and NSAG |
CATT |
| R2-2207932 |
Cleanup on RAN Slicing |
Apple |
| R2-2207933 |
CR on slice availability provision for serving cell |
Apple |
| R2-2207934 |
CR to cleanup slice specific cell reselection |
Apple |
| R2-2207952 |
Discussion on the details of slice specific cell reselection |
Huawei, HiSilicon |
| R2-2207953 |
Corrections on TS 38.304 for RAN Slicing |
Huawei, HiSilicon |
| R2-2208003 |
Support of RAN sharing and equivalent PLMNs with slice specific cell reselection |
Nokia, Nokia Shanghai Bell |
| R2-2208143 |
Corrections on slice-based cell re-selection in TS 38.304 |
Ericsson |
| R2-2208296 |
Possible configuration mismatch in slice specific cell reselection |
Kyocera |
| R2-2208446 |
Correction on the rules in equal priority case for slice-based cell reselection |
CMCC, OPPO, Huawei, HiSilicon |
| R2-2208495 |
Slice specific reselection priorities in RRC Release |
Samsung R&D Institute India |
| R2-2208517 |
Correction on per-TA NSAG for slice specific cell reselection |
Qualcomm Incorporated |
| R2-2208519 |
Issues with slice specific cell reselection |
Samsung R&D Institute India |
| R2-2208607 |
38.304 CR Corrections on slice-based cell reselection |
Xiaomi, OPPO, CMCC |
| R2-2208690 |
Correction on TS 38.331 for RAN slicing |
CATT |
| R2-2208729 |
Report of [AT119-e][240][Slicing] RRC, MAC and Stage-2 CRs to RAN slicing (Huawei) |
Huawei |
| R2-2208730 |
Corrections on TS 38.300 for RAN Slicing |
Huawei, HiSilicon |
| R2-2208731 |
Corrections on TS 38.321 for RAN Slicing |
Huawei, HiSilicon, OPPO |
| R2-2208732 |
Corrections to TS 38.331 for RAN Slicing |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2208733 |
Report of [AT119-e][241][Slicing] Cell reselection corrections to RAN slicing (Qualcomm) |
Qualcomm |
| R2-2208734 |
Correction on per-TA NSAG for slice specific cell reselection |
Qualcomm Incorporated |
| R2-2209224 |
Corrections on TS 38.300 for RAN Slicing |
Huawei, HiSilicon |
| R2-2209225 |
Corrections on TS 38.321 for RAN Slicing |
Huawei, HiSilicon, OPPO |
| R2-2209226 |
Corrections on TS 38.331 for RAN Slicing |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2209228 |
Cell reselection corrections to RAN slicing |
Qualcomm Incorporated, Samsung |
| 6.8.3 |
RACH |
|
| R2-2207471 |
38.300 CR Corrections on slice based RACH configuration |
Beijing Xiaomi Software Tech |
| R2-2207798 |
Minor correction on slice-specific RACH |
OPPO |
| R2-2208142 |
Miscellaneous corrections for RAN slicing enhancements |
Ericsson |
| 6.9.1 |
Organizational and Stage-2 |
|
| R2-2206932 |
Reply LS on PEI and UE Subgrouping (R3-224004; contact: ZTE) |
RAN3 |
| R2-2207070 |
Stage-2 correction on UE-ID based subgrouping |
OPPO |
| R2-2207745 |
Correction on idle/inactive TRS for ePowSav |
vivo |
| R2-2208015 |
Stage 2 correction on power saving |
Nokia, Nokia Shanghai Bell |
| R2-2208227 |
Corrections for UE power saving enhancements In 38.300 |
Huawei, HiSilicon |
| R2-2209007 |
Summary of [AT119-e][029][ePowSav] Stage-2 38300 |
Huawei, HiSilicon |
| R2-2209008 |
Corrections to UE power saving enhancements in TS 38.300 |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R2-2209152 |
LS on PDCCH skipping (R1-2208210; contact: MediaTek) |
RAN1 |
| R2-2209162 |
Reply LS to RAN2 on RLM/BFD relaxation (R4-2214475; contact: vivo) |
RAN4 |
| 6.9.2 |
Control Plane |
|
| R2-2207005 |
Clarification of PEI monitoring related parameters |
Samsung Electronics Co., Ltd |
| R2-2207051 |
Correction to UE ID based subgrouping |
OPPO |
| R2-2207071 |
Correction on RLM/BFD relaxation for SCG deactivation – alternative 1 |
OPPO |
| R2-2207072 |
Correction on RLM/BFD relaxation for SCG deactivation – alternative 2 |
OPPO |
| R2-2207206 |
38.331 Corrections on PDCCH-ConfigCommon for PEI |
Xiaomi Communications |
| R2-2207398 |
Miscellaneous CR on TS 38.331 for ePowSav |
CATT, Xiaomi |
| R2-2207399 |
Consideration on RLM/BFD relaxation configuration with bfd-and-RLM |
CATT |
| R2-2207403 |
BFD/RLM relaxation for deactivated SCG |
Fujitsu |
| R2-2207404 |
BFD relaxation for serving cell with mTRP |
Fujitsu |
| R2-2207538 |
Clarification on the state report of RLM BFD relaxation |
Sharp |
| R2-2207742 |
Miscellaneous CR on TS 38.304 for ePowSav |
vivo |
| R2-2207743 |
Remaining issues on RLM/BFD relaxation |
vivo |
| R2-2207744 |
Correction on RLM/BFD relaxation and PEI configuration |
vivo |
| R2-2208016 |
Clarification on PEI and subgrouping capability |
Nokia, Nokia Shanghai Bell |
| R2-2208017 |
Clarification on subgrouping descriptions |
Nokia, Nokia Shanghai Bell |
| R2-2208091 |
RLM and BFD relaxation status reporting for deactivated SCG |
Ericsson |
| R2-2208224 |
Corrections on the prohibit timer for RLM/BFD relaxation and the TRS availability |
Huawei, HiSilicon |
| R2-2208225 |
Discussion on RLM/BFD relaxation and SCG deactivation |
Huawei, HiSilicon |
| R2-2208226 |
Correction on the UE_ID based subgrouping |
Huawei, HiSilicon |
| R2-2208334 |
Clarification on paging early indication with paging subgrouping during emergency call |
MediaTek Inc. |
| R2-2208554 |
CR on 38.304 for PEI and pagingsubgrouping |
ZTE Corporation,Sanechips |
| R2-2208555 |
CR for the field description of searchspaceGroupList and general description of RLMBFD relaxation |
ZTE Corporation,Sanechips |
| R2-2208609 |
38.304 Clarifications on SubgroupID for UE-ID based subgrouping |
Xiaomi, ZTE Corporation,Vivo, Ericsson, CATT |
| R2-2208909 |
[Pre119-e][004][ePowSav] Subgrouing/PEI Summary (MediaTek) |
MediaTek |
| R2-2208922 |
Summary of RLM BFD relaxation |
vivo |
| R2-2209003 |
Report of [AT118-e][003][ePowSav] RLM and BFD relaxation (vivo) |
vivo |
| R2-2209018 |
Report of [AT119-e][004][ePowSav] Subgrouping/PEI (MediaTek) |
MediaTek |
| R2-2209130 |
LS to RAN4 on RLM/BFD relaxation for ePowSav |
RAN2 |
| R2-2209200 |
Miscellaneous CR on TS 38.331 for ePowSav |
CATT, Xiaomi, ZTE Corporation |
| R2-2209227 |
Miscellaneous CR on TS 38.304 for ePowSav |
vivo |
| 6.9.3 |
User Plane |
|
| R2-2208089 |
PDCCH monitoring adaptation and C-DRX (RIL V146) |
Ericsson |
| R2-2208090 |
PDCCH skipping in RAN1 and RAN2 specifications |
Ericsson |
| R2-2209012 |
Summary of [AT119-e][028][ePowSav] PDCCH Skip |
Ericsson |
| 6.10.1 |
Organizational |
|
| R2-2209161 |
LS to RAN2 on Network indication for applying enhanced cell reselection requirements (R4-2214472; contact: Huawei) |
RAN4 |
| 6.10.1.1 |
LS in |
|
| R2-2206948 |
Reply LS on measurement gap enhancements for NTN (R4-2210611; contact: Intel) |
RAN4 |
| R2-2206968 |
LS reply on Reply LS on NTN specific User Consent and UE location in connected mode in NTN (S3-221268; contact: Ericsson) |
SA3 |
| R2-2207067 |
Discussion on CT1 LS on not allowed PLMN at the current location |
OPPO |
| R2-2207271 |
Discussion on RAN4 reply LS on measurement gaps |
Intel Corporation |
| R2-2208760 |
Summary of [AT119-e][109][NR-NTN] Stage-2 CR (Thales) |
Thales |
| R2-2209191 |
Reply LS on the deactivation of access stratum due to discontinuous coverage (S2-2207420; contact: Qualcomm) |
SA2 |
| 6.10.1.2 |
Rapporteur inputs |
|
| R2-2207065 |
NTN Stage-2 correction |
OPPO, Thales |
| R2-2207097 |
Draft Summary for NR support for Non-Terrestrial Networks (NTN) |
THALES |
| R2-2207322 |
Rel-17 NTN Stage-2 (Rapporteur) corrections |
Nokia, Nokia Shanghai Bell |
| R2-2207924 |
Corrections for Release-17 NTN |
Ericsson |
| R2-2207927 |
Corrections for Release-17 NTN RRC |
Ericsson |
| R2-2208272 |
Corrections to Release-17 NR Non-Terrestrial Networks (NTN): RAN2#119e |
InterDigital |
| R2-2208329 |
Miscellaneous corrections on 38.304 |
ZTE Corporation, Sanechips, CMCC, vivo, Apple |
| R2-2208761 |
Rel-17 NTN Stage-2 (Rapporteur) corrections |
Nokia, Nokia Shanghai Bell |
| R2-2208776 |
Corrections to Release-17 NR Non-Terrestrial Networks (NTN): RAN2#119e |
InterDigital |
| R2-2208783 |
Miscellaneous corrections on 38.304 |
ZTE Corporation, Sanechips, CMCC, vivo, Apple, Nokia, Nokia Shanghai Bell, CATT |
| R2-2208787 |
Draft 331 CR for NR NTN UE capabilities |
Intel Corporation |
| R2-2208788 |
Draft 306 CR for NR NTN UE capabilities |
Intel Corporatio |
| R2-2208925 |
Draft Summary for NR support for Non-Terrestrial Networks (NTN) |
THALES |
| R2-2208935 |
Draft Summary for NR support for Non-Terrestrial Networks (NTN) |
THALES |
| R2-2209042 |
Corrections for Release-17 NTN |
Ericsson |
| R2-2209044 |
Corrections to Release-17 Non-Terrestrial Networks (NTN) for TS 38.321 |
InterDigital |
| R2-2209046 |
Rel-17 NTN related Rapporteur's corrections to TS 38.300 |
Thales, Nokia, Nokia Shanghai Bell |
| R2-2209247 |
Corrections for Release-17 NTN |
Ericsson |
| 6.10.2.1 |
MAC corrections |
|
| R2-2207240 |
Discussion on TA report |
Samsung Research America |
| R2-2207241 |
Discussion on remaining MAC issues |
Samsung Research America |
| R2-2207443 |
NTN UL synchronization correction in MAC |
Apple |
| R2-2207596 |
Discussion on the issue of outdated UE TA at NW side |
Huawei, HiSilicon |
| R2-2207598 |
Correction on maintenance of UL synchronization in MAC |
Huawei, HiSilicon |
| R2-2207628 |
Remaining issue on UL synchronization in NR NTN |
vivo |
| R2-2207629 |
On corrections to random access procedure in NR NTN |
vivo |
| R2-2208273 |
Blind Msg3 retransmission in Rel-17 NTN |
InterDigital |
| R2-2208274 |
SR configuration for Timing Advance MAC CE |
InterDigital |
| R2-2208275 |
Clarifications to the Timing Advance reporting procedure |
InterDigital |
| R2-2208382 |
Correction on TA Reporting Triggering Condition for NTN in TS 38.321 |
CATT |
| R2-2208560 |
On issues for Timing Advance Report MAC CE |
Nokia, Nokia Shanghai Bell |
| R2-2208569 |
Remaining UP issues in NTN |
ZTE Corporation, Sanechips |
| R2-2208570 |
Correction to 38321 on TA report |
ZTE Corporation, Sanechips |
| R2-2208571 |
Correction to 38321 on ra-ContentionResolutionTimer |
ZTE Corporation, Sanechips |
| R2-2208576 |
Clarification on the condition of contention resolution not successful |
Xiaomi |
| R2-2208675 |
R17 NR NTN User Plane issues |
Ericsson |
| R2-2208751 |
Report of [AT119-e][101][NTN] UP corrections |
InterDigital |
| R2-2208763 |
Report of [AT119-e][101][NTN] UP corrections: Phase 2 |
InterDigital |
| 6.10.2.2 |
Other |
|
| R2-2207052 |
left issues on UP in NTN |
OPPO |
| R2-2207341 |
Outdated UE specific Koffset |
Qualcomm Incorporated |
| R2-2207671 |
Discussion on the RA counter in case of ephemeris update |
Spreadtrum Communications |
| R2-2208561 |
On Msg3 blind retransmission and UE behaviour upon validity timer expiry |
Nokia, Nokia Shanghai Bell |
| R2-2208678 |
R17 NR NTN stage 2 corrections |
Ericsson |
| 6.10.3.1 |
Idle inactive mode corrections |
|
| R2-2207323 |
Rel-17 NTN IDLE mode corrections |
Nokia, Nokia Shanghai Bell |
| R2-2207440 |
Clarification on the suitable cell in NTN |
Apple |
| R2-2207632 |
Clarification on time-based cell reselection in TS 38.304 |
vivo |
| R2-2207863 |
Discussion on the acquisition and prediction of ephemeris for SIB19 |
BUPT |
| R2-2208094 |
R17 NR NTN Idle mode corrections |
Ericsson |
| R2-2208137 |
Correction on Measurement rules for cell re-selection for NR NTN |
Samsung R&D Institute UK |
| R2-2208379 |
Miscellaneous corrections on 38.304 |
CATT |
| R2-2208764 |
Report of [AT119-e][110][NR-NTN] Idle mode corrections (ZTE) |
ZTE corporation,Sanechips |
| 6.10.3.2.1 |
SMTC and gaps |
|
| R2-2207068 |
Correction on NTN UE capabiltiy |
OPPO |
| R2-2207149 |
Remaining issues on SMTCs and gaps |
Huawei, HiSilicon |
| R2-2207242 |
Discussion on SMTC related issues |
Samsung Research America |
| R2-2207243 |
Draft 331 CR for NR NTN SMTC |
Samsung Research America |
| R2-2207268 |
Draft 331 CR for NR NTN measurement related UE capabilities |
Intel Corporation |
| R2-2207269 |
Draft 306 CR for NR NTN measurement related UE capabilities |
Intel Corporation |
| R2-2207270 |
Discussion on UE capability for 2 SMTC in parallel |
Intel Corporation |
| R2-2207344 |
Correction to the frame boundary alignment indication from the source |
Qualcomm Incorporated |
| R2-2207345 |
Reporting SMTC issue in measurement results |
Qualcomm Incorporated |
| R2-2208214 |
Correction to associate two concurrent measurement gaps to one frequency layer for NR NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208466 |
Correction for measurement gap |
Xiaomi |
| R2-2208752 |
Report of [AT119-e][102][NR-NTN] SMTC and gaps (Intel) |
Intel Corporation |
| R2-2208765 |
Report of [AT119-e][102][NR-NTN] SMTC and gaps (Intel) - second round |
Intel Corporation |
| 6.10.3.2.2 |
CHO |
|
| R2-2207672 |
Discussion on the ephemeris information in CHO procedure |
Spreadtrum Communications |
| R2-2208534 |
Correction of entering and leaving condition of CondEventT1 |
LG Electronics France |
| 6.10.3.2.3 |
Other |
|
| R2-2207053 |
Correction to RRC-MAC interaction on UL synchronisation in NTN |
OPPO |
| R2-2207063 |
Discussion on how to handle the validity timer for neighbor cells |
OPPO |
| R2-2207066 |
NTN RRC correction |
OPPO |
| R2-2207141 |
Correction of UE location aspects in NTN |
Thales, Xiaomi |
| R2-2207144 |
Correction of UE location aspects in NTN |
Thales, Xiaomi |
| R2-2207148 |
Remaining issues on ephemeris provision |
Huawei, HiSilicon, Thales |
| R2-2207324 |
Rel-17 NTN corrections to NR RRC |
Nokia, Nokia Shanghai Bell |
| R2-2207342 |
Same ULTSRP indication of the target cell during handover |
Qualcomm Incorporated |
| R2-2207343 |
List of frequencies and satellite index for a neighbor satellite in SIB19 |
Qualcomm Incorporated |
| R2-2207439 |
Clarification on the necessity of SIB19 in NTN cell |
Apple |
| R2-2207441 |
The impact on HO by the validity of the UL sync assistance info |
Apple |
| R2-2207442 |
Clarification on the features supported in NTN network |
Apple |
| R2-2207597 |
Discussion on the UE location reporting |
Huawei, HiSilicon |
| R2-2207630 |
Correction on access restriction for NR NTN in TS 38.331 |
vivo |
| R2-2207631 |
Remaining issues on validity timer in NR NTN |
vivo |
| R2-2207769 |
Corrections to TA Report in RRC Connection Reestablishment |
Google Inc. |
| R2-2207777 |
Corrections to TA Report in RRC Connection Resume |
Google Inc. |
| R2-2207889 |
Discussion on whether the inactive state of RRC enables in specific scenarios for NTN |
BUPT |
| R2-2208288 |
Correction to coarseLocationInfo field description for NR NTN |
Eutelsat S.A. |
| R2-2208362 |
Discussion on validity timer for serving cell and neighbour cell |
ASUSTeK |
| R2-2208363 |
Discussion on T430 for handover |
ASUSTeK |
| R2-2208364 |
Discussion on configuration of harq-ProcessNumberSizeDCI-0-2 |
ASUSTeK |
| R2-2208378 |
Discussion on Neighbor Satellite Assistance Information |
CATT |
| R2-2208380 |
Miscellaneous corrections on 38.300 |
CATT |
| R2-2208381 |
Miscellaneous corrections on 38.331 |
CATT |
| R2-2208537 |
Corrections to NTN capabilities |
LG Electronics |
| R2-2208538 |
Miscellaneous corrections for NTN |
LG Electronics |
| R2-2208575 |
correction on coarselocationrequest |
Xiaomi, Thales |
| R2-2208577 |
correction on triggering TA report during HO |
Xiaomi |
| R2-2208578 |
Correction on missing the action upon not being able to acquire SIB19 |
Xiaomi |
| R2-2208657 |
Issues related to NR NTN epoch time |
Sequans Communications |
| R2-2208659 |
NTN Configuration at Handover and CHO |
Sequans Communications |
| R2-2208679 |
R17 NR NTN UE Capability issues |
Ericsson |
| R2-2208753 |
Summary of [AT119-e][103][NR-NTN] Other RRC corrections (OPPO) |
OPPO |
| R2-2208766 |
Summary of [AT119-e][103][NR-NTN] Other RRC corrections (OPPO) |
OPPO |
| R2-2208767 |
[AT119-e][111][NR-NTN] RRC corrections (Ericsson) |
Ericsson |
| R2-2208777 |
[AT119-e][111][NR-NTN] RRC corrections- second round (Ericsson) |
Ericsson |
| R2-2208782 |
Summary of [AT119-e][103][NR-NTN] Other RRC corrections (OPPO) - phase 3 |
OPPO |
| R2-2208908 |
Summary of 6.10.3.2.3 on R17 NR NTN (Other) RRC corrections |
OPPO |
| R2-2208970 |
correction on triggering TA report during HO |
Xiaomi |
| 6.11.1 |
Organizational |
|
| R2-2206903 |
Response LS to RTCM SC134 on GNSS integrity (RTCM; contact: ESA) |
RTCM |
| R2-2206914 |
Reply LS on the UE/TRP TEG framework (R1-2205382; contact: CATT) |
RAN1 |
| R2-2206916 |
LS on updates of RRC parameters for Rel-17 positioning enhancements (R1-2205406; contact: CATT) |
RAN1 |
| R2-2206919 |
Reply LS on lower Rx beam sweeping factor for latency improvement (R1-2205450; contact: Huawei) |
RAN1 |
| R2-2206927 |
Reply LS on expected AoA and AoD parameters (R1-2205619; contact: Nokia) |
RAN1 |
| R2-2206945 |
Further reply LS on condition for PRS measurement outside the MG (R4-2210601; contact: Huawei) |
RAN4 |
| R2-2206946 |
LS on Tx TEG framework (R4-2210603; contact: CATT) |
RAN4 |
| R2-2206947 |
LS on switching time for SRS transmission outside initial UL BWP in RRC_INACTIVE (R4-2210604; contact: Huawei) |
RAN4 |
| R2-2207099 |
Corrections on the RxTEG,TxTEG and RxTxTEG report in TS 37.355 |
CATT |
| R2-2207100 |
Corrections on the UE TxTEG report in TS 38.331 |
CATT |
| R2-2207384 |
Mscellaneous corrections for TS38.305 |
Intel Corporation |
| R2-2207385 |
Corrections on LPP capabilies |
Intel Corporation |
| R2-2207880 |
Editor's Correction for MAC spec for Positioning |
Huawei, HiSilicon |
| R2-2208076 |
Miscellaneous correction for Positioning |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2208710 |
RRC Corrections for Positioning |
Ericsson |
| R2-2208801 |
Mscellaneous corrections for TS38.305 |
Intel Corporation |
| R2-2208802 |
Corrections on LPP capabilies |
Intel Corporation |
| R2-2208805 |
[AT119-e][419][POS] LS from RTCM (Ericsson) |
Ericsson |
| R2-2208816 |
Report of [AT119-e][408][POS] Rel-17 positioning stage 2 (Intel) |
Intel Corporation |
| R2-2208817 |
Report of [AT119-e][409][POS] Rel-17 positioning capabilities (Intel) |
Intel Corporation |
| R2-2208818 |
Editor's Correction for MAC spec for Positioning |
Huawei, HiSilicon |
| R2-2208819 |
[Offline-410][POS] Rel-17 positioning MAC (Huawei) |
Huawei, HiSilicon |
| R2-2208825 |
Miscellaneous correction for Positioning |
Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2208940 |
LS to RAN1 and RAN4 on DL-PRS sample capability |
ZTE Corporation |
| R2-2208946 |
Summary of [Post119-e][411][POS] Positioning 38.321 CR (Huawei) |
Huawei |
| R2-2208947 |
Change to the MAC spec for R17 Positioning enhancement |
Huawei, HiSilicon |
| R2-2209110 |
LS on SRS-PosRRC-InactiveConfig configuration signalling (R3-225268; contact: Intel) |
RAN3 |
| R2-2209114 |
[Offline-410][POS] Rel-17 positioning MAC (Huawei)_round 2 |
Huawei, HiSilicon |
| R2-2209120 |
Reply LS on DL-PRS measurements with reduced samples capability (R1-2207940; contact: ZTE) |
RAN1 |
| R2-2209156 |
Reply LS on LocationMeasurementIndication contents and measurement gap parameters (R4-2214335; contact: Huawei) |
RAN4 |
| R2-2209167 |
Reply LS on DL-PRS measurements with reduced samples capability (R4-2214489; contact: CATT) |
RAN4 |
| R2-2209168 |
Reply LS on the UE/TRP TEG framework (R4-2214493; contact: CATT) |
RAN4 |
| R2-2209195 |
LS response on GNSS integrity (S2-2207691; contact: Huawei) |
SA2 |
| R2-2209232 |
Summary of [Post119-e][413][POS] 37.355 CR (Qualcomm) |
Qualcomm Incorporated |
| R2-2209237 |
Miscellaneous correction for Positioning |
Ericsson, Nokia, Nokia Shanghai Bell, vivo, Qualcomm Incorporated, Huawei, ZTE, CATT |
| R2-2209238 |
Summary of [Post119-e][412][POS] Positioning 38.331 CR (Ericsson) |
Ericsson |
| R2-2209239 |
Corrections on LPP capabilities |
Intel Corporation |
| R2-2209240 |
Mscellaneous corrections for TS38.305 |
Intel Corporation (running CR Rapporteur) |
| R2-2209241 |
LS to RAN4 on capability for PRS measurement without MG |
RAN2 |
| 6.11.2 |
Essential corrections |
|
| R2-2208298 |
Discussion on positioning of UEs in FR2-2 |
Samsung |
| R2-2208299 |
Clarification on the use of SRS with 480 kHz, 960 kHz SCS in FR2-2 for positioning |
Samsung |
| R2-2208967 |
LS on support of positioning in FR2-2 |
Samsung |
| 6.11.2.1 |
Latency enhancements |
|
| R2-2207101 |
Corrections on the latency enhancements in TS 37.355 |
CATT |
| R2-2207110 |
Corrections on TS38.305 |
CATT |
| R2-2207411 |
Change request about PPW configuration |
vivo, Ericsson |
| R2-2207579 |
Correction on the request message of reduced PRS samples in 37.355 |
ZTE, Sanechips |
| R2-2207580 |
Correction on UE capability of reduced PRS samples in RRC_INACTIVE in 37.355 |
ZTE, Sanechips |
| R2-2207693 |
Positioning during handover and re-establishment |
Lenovo |
| R2-2207885 |
Correction to the number of samples for PRS measurement in RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2207886 |
Cancellation of SR for posMG (de-)activation request |
Huawei, HiSilicon |
| R2-2208077 |
Correction of the IE for lower Rx beam sweeping factor than 8 for FR2 capability and request |
Ericsson |
| R2-2208124 |
Correction to missing Scheduling Request Configuration for Positioning Measurement Gap Activation/Deactivation Request MAC CE |
Qualcomm Incorporated |
| R2-2208125 |
Correction to Scheduling Request for Positioning Measurement Gap Activation/Deactivation Request |
Qualcomm Incorporated |
| R2-2208204 |
Miscellaneous corrections to NR positioning enhancements |
Lenovo |
| R2-2208300 |
Cancellation of UL MAC CE for MG activation/deactivation |
Samsung |
| R2-2208491 |
Change request about validity area in 38.305 |
vivo |
| R2-2208492 |
Change request about UE capability for PRS measurement within a PPW |
vivo |
| R2-2208512 |
Corrections for triggered Positioning MG Req MAC CE |
Samsung |
| R2-2208686 |
Correction on PPW for positioning enhancement |
NEC |
| R2-2208792 |
Summary of AI 6.11.2.1: Essential Corrections for Latency enhancements |
Qualcomm Incorporated |
| R2-2208797 |
LS on DL-PRS measurements with reduced samples capability |
RAN2 |
| R2-2208800 |
Miscellaneous LPP Corrections |
Qualcomm Incorporated |
| R2-2208803 |
Summary of [AT119-e][424][POS] Rel-17 LPP CR (Qualcomm) |
Qualcomm Incorporated |
| R2-2208811 |
LS on SR config for MG (de-)activation request MAC CE |
RAN2 |
| R2-2209231 |
Miscellaneous LPP Corrections |
Qualcomm Incorporated (Rapporteur) |
| 6.11.2.2 |
RRC_INACTIVE |
|
| R2-2207112 |
Discussion on left over issues of UL positioning in RRC_Inactive |
CATT |
| R2-2207881 |
Correction for inactivePosSRS-TAT upon transitioning to RRC_CONNECTED |
Huawei, HiSilicon |
| R2-2207883 |
Correction to TA-validation for inactive SRS transmission |
Huawei, HiSilicon |
| R2-2208074 |
on RRC Inactive Mode Positioning |
Ericsson |
| R2-2208521 |
Corrections on activation and deactivation of SP-SRSp transmission in RRC INACTIVE |
Xiaomi, Huawei, vivo |
| R2-2208806 |
[AT119-e][421][POS] Delta configuration for SRSp in RRC_INACTIVE (CATT) |
CATT |
| 6.11.2.3 |
On-demand PRS |
|
| R2-2207012 |
Corrections for DL-PRS processing window activation |
Samsung Electronics Co., Ltd |
| R2-2207419 |
Change request about QCL-Info in the on-demand PRS request |
vivo |
| R2-2208493 |
Discussion on the format of on-demand PRS configuration |
vivo, ZTE, Ericsson, Huawei, Xiaomi |
| 6.11.2.4 |
GNSS positioning integrity |
|
| R2-2207363 |
Corrections on the integrity of A-GNSS in TS 37.355 |
CATT |
| R2-2207736 |
Corrections on the integrity of A-GNSS in TS 37.355 |
CATT |
| R2-2208075 |
Provisioning of missing integrity requirements |
Ericsson |
| R2-2208395 |
Correction on the GNSS Orbit and Clock Integrity Bounds in TS 37.355 |
Swift Navigation, ESA, Ericsson |
| R2-2208415 |
Correction on the mean orbit error projection in TS 38.305 |
Swift Navigation, ESA, Ericsson |
| R2-2208419 |
Correction on the mean orbit error projection in TS 36.305 |
Swift Navigation, ESA, Ericsson |
| R2-2208793 |
(Email summary on LPP proposals in AI 6.11.2.4) |
Swift Navigation |
| R2-2208807 |
[AT119-e][425][POS] UE-based integrity assessment (Ericsson) |
Ericsson |
| R2-2208827 |
Correction on the GNSS Orbit and Clock Integrity Bounds in TS 37.355 |
Swift Navigation, ESA, Ericsson |
| 6.11.2.6 |
Accuracy enhancements |
|
| R2-2207087 |
37.355 CR for clarification of number of UE Rx TEGs |
OPPO |
| R2-2207088 |
37.355 CR for introduction of UE Rx TEG error margin and Tx TEG error margin |
OPPO |
| R2-2207102 |
Corrections on the accuracy enhancements in TS 37.355 |
CATT |
| R2-2207578 |
Correction on additional measurements in 37.355 |
ZTE, Sanechips |
| R2-2207581 |
Correction on UE Rx Tx RxTx TEG and TRP Tx TEG timing error margin in 37.355 |
ZTE, Sanechips |
| R2-2207582 |
Correction on UE Tx TEG timing error margin in 38.331 |
ZTE, Sanechips |
| R2-2207583 |
Discussion on the framework of TEG timing error margin |
ZTE, Sanechips |
| R2-2207882 |
Correction to measurment with mutliple TEGs |
Huawei, HiSilicon, VIVO |
| R2-2207884 |
Correction to DL-AoD measurement report |
Huawei, HiSilicon |
| R2-2208073 |
On Mitigation of UE/TRP Rx/Tx timing delays |
Ericsson |
| R2-2208494 |
Change request about description of RSPP and RSRPP in 38.305 |
vivo |
| R2-2208794 |
[Pre119-e][402] Summary of agenda item 6.11.2.6 on positioning accuracy enhancements (CATT) |
CATT |
| R2-2208808 |
[AT119-e][426][POS] TEG timing error margin in RRC and LPP (CATT) |
CATT |
| R2-2208830 |
[AT119-e][426][POS] TEG timing error margin in RRC and LPP (CATT) |
CATT |
| 6.12.1 |
Organizational |
|
| R2-2209164 |
Reply LS on configuring margin for 1 Rx RedCap Ues (R4-2214484; contact: Ericsson) |
RAN4 |
| R2-2209165 |
Reply LS on RRM relaxation for Redcap (R4-2214487; contact: vivo) |
RAN4 |
| R2-2209166 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times (R4-2214488; contact: Huawei) |
RAN4 |
| R2-2209205 |
Reply LS on the maximum PTW length of IDLE eDRX (C1-225450; contact: Qualcomm) |
CT1 |
| 6.12.1.1 |
LS in |
|
| R2-2206924 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times (R1-2205535; contact: Ericsson) |
RAN1 |
| R2-2206941 |
LS on CGI reading with autonomous gaps for RedCap (R4-2210593; contact: Ericsson) |
RAN4 |
| R2-2206942 |
LS on measurement capability for RedCap (R4-2210594; contact: CMCC) |
RAN4 |
| R2-2206943 |
Reply LS on RRM relaxation for Redcap (R4-2210598; contact: vivo) |
RAN4 |
| R2-2206944 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times (R4-2210599; contact: Ericsson) |
RAN4 |
| R2-2209102 |
Reply LS on introduction of an offset to transmit CD-SSB and NCD-SSB at different times (R1-2207980; contact: Ericsson) |
RAN1 |
| R2-2209128 |
LS on common PUCCH resource configuration for RedCap (R1-2208208; contact: Ericsson) |
RAN1 |
| 6.12.1.2 |
Rapporteur inputs |
|
| R2-2207746 |
Miscellaneous CR on TS 38.321 for RedCap |
vivo |
| R2-2208219 |
Corrections on RedCap in TS 38.300 |
Nokia, Nokia Shanghai Bell, Huawei |
| R2-2208306 |
Miscellaneous corrections for RedCap WI |
Ericsson |
| R2-2208307 |
Miscellaneous corrections for RedCap WI |
Ericsson |
| R2-2208769 |
[AT119-e][113][RedCap] Stage-2 CR (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2208770 |
Corrections on RedCap in TS 38.300 |
Nokia, Nokia Shanghai Bell, Huawei |
| R2-2208778 |
Miscellaneous corrections for RedCap WI |
Ericsson |
| R2-2208950 |
Corrections on RedCap in TS 38.300 |
Nokia, Nokia Shanghai Bell, Huawei |
| R2-2209048 |
Miscellaneous corrections for RedCap WI |
Ericsson |
| R2-2209049 |
Miscellaneous CR on TS 38.321 for RedCap |
vivo |
| 6.12.2.1 |
NCD-SSB aspects |
|
| R2-2207041 |
Clarification on reference SSB for intra- and inter-frequency measurements for RedCap UEs |
Qualcomm Incorporated |
| R2-2207464 |
CR on handling time domain offset of CD and NCD-SSB |
Apple |
| R2-2207465 |
CR on handling time domain offset of CD and NCD-SSB |
Apple |
| R2-2207619 |
Remaining issues on NCD-SSB for RedCap |
Huawei, HiSilicon |
| R2-2207747 |
Discussion on NCD SSB for RedCap UEs |
vivo, Guangdong Genius |
| R2-2207748 |
Correction on RRC for RedCap |
vivo, Guangdong Genius |
| R2-2207995 |
Clarification of BWP operation in Connected mode |
MediaTek Inc. |
| R2-2208111 |
Correction on RedCap-specific initial BWP |
ZTE Corporation, Sanechips |
| R2-2208136 |
Correction to definition and values of ssb-TimeOffset for NCD-SSB |
Qualcomm Incorporated |
| R2-2208308 |
Clarification on the field description of rach-ConfigCommonfor for RedCap UEs |
Ericsson |
| R2-2208311 |
Introducing capability bit for RedCap UEs to indicate NCD-SSB support |
Ericsson |
| R2-2208383 |
Correction on description of SSB based intra-frequency measurement for RedCap UE |
CATT |
| R2-2208398 |
CR for RACH operation during SI update when the active BWP contains no CD-SSB |
LG Electronics Inc. |
| R2-2208774 |
Report of [AT119-e][117][RedCap] NCD-SSB Corrections (ZTE) |
ZTE Corporation |
| R2-2208786 |
Report of [AT119-e][117][RedCap] NCD-SSB Corrections - second round (ZTE) |
ZTE Corporation |
| 6.12.2.2 |
Other RRC corrections |
|
| R2-2207054 |
Clarification on support of eDRX |
OPPO |
| R2-2207055 |
Clarification on UE support of eDRX |
OPPO |
| R2-2207069 |
Discussion on inter-RAT mobility from LTE to NR |
OPPO |
| R2-2207209 |
38.331 Corrections on PDCCH-ConfigCommon for Redcap |
Xiaomi Communications |
| R2-2207230 |
Correction on inter-RAT handover from E-UTRA to NR for RedCap |
Sequans Communications, Huawei, HiSilicon |
| R2-2207386 |
Alignment on the support of 2TX and 2UL MIMO for RedCap UEs |
Intel Corporation, Huawei |
| R2-2207620 |
Corrections on PDCCH-ConfigCommon for RedCap initial BWP |
Huawei, HiSilicon |
| R2-2207621 |
Corrections on the relaxed measurement criterion and smtc field for RedCap |
Huawei, HiSilicon |
| R2-2207749 |
Correction on capability for RedCap |
vivo, Guangdong Genius |
| R2-2207751 |
Correction on TS 38.300 for RedCap |
vivo |
| R2-2207996 |
Inter-RAT handover from LTE to NR |
MediaTek Inc. |
| R2-2208155 |
Correction on UERadioPagingInformation and UERadioPagingInfo container |
Ericsson |
| R2-2208309 |
Clarification on the field description of commonControlResourceSet for RedCap UEs |
Ericsson |
| R2-2208310 |
Paging configuration for RedCap UEs in the initial DL BWP |
Ericsson |
| R2-2208385 |
Corrections on RedCap specific initial DL BWP related description |
CATT |
| R2-2208386 |
Discussion and TP on the SI request on SUL for RedCap |
CATT |
| R2-2208438 |
Remaining aspect on RedCap initial DL BWP |
CMCC |
| R2-2208439 |
Corrections on RedCap initial DL BWP |
CMCC |
| R2-2208631 |
Correction on eDRX allowed indication and PDCCH-ConfigCommon |
ZTE Corporation, Sanechips |
| R2-2208632 |
Correction on eDRX allowed indication and BFD |
ZTE Corporation, Sanechips |
| R2-2208772 |
Report from [AT119-e][115][RedCap] CP Corrections (Ericsson) |
Ericsson (Rapporteur) |
| R2-2208790 |
Report from [AT119-e][115][RedCap] CP Corrections (Ericsson) |
Ericsson (Rapporteur) |
| R2-2208924 |
Correction on PUCCH-ConfigCommon for RedCap UE |
ZTE Corporation, Sanechips |
| R2-2208932 |
On PUCCH configuration in initial UL BWP |
MediaTek Inc. |
| R2-2209045 |
Report from [AT119-e][116][RedCap] Idle mode CR (Ericsson) |
Ericsson (Rapporteur) |
| 6.12.2.3 |
Idle inactive mode corrections |
|
| R2-2207007 |
Correction to description of first-PDCCH-MonitoringOccasionOfPO |
Samsung Electronics Co., Ltd |
| R2-2207207 |
38.304 Correction on the e-DRX for Redcap |
Xiaomi Communications |
| R2-2207622 |
Corrections on the intra-FreqReselection and eDRX supporting for RedCap |
Huawei, HiSilicon |
| R2-2207750 |
Discussion on cellBar for RedCap |
vivo, Guangdong Genius |
| R2-2208112 |
Miscellaneous correction on eDRX |
ZTE Corporation, Sanechips |
| R2-2208221 |
Correction on eDRX-Allowed indication |
Nokia, Nokia Shanghai Bell |
| 6.12.3.1 |
MAC aspects |
|
| R2-2207008 |
BWP Switching upon SI request ack |
Samsung Electronics Co., Ltd |
| R2-2207009 |
BWP Switching in RRC_IDLE_RRC_INACTIVE_upon RA initiation |
Samsung Electronics Co., Ltd |
| R2-2207010 |
Corrections to BWP inactivity timer (re)start criteria upon reception of PDCCH for BWP switching |
Samsung Electronics Co., Ltd |
| R2-2207208 |
38.321 Correction on the BWP operations for Redcap |
Xiaomi Communications |
| R2-2207903 |
RedCap support for sending BFR MAC CE for SpCell BFR |
Nokia, Nokia Shanghai Bell |
| R2-2207904 |
Correction on RedCap support for sending BFR MAC CE for SpCell BFR |
Nokia, Nokia Shanghai Bell |
| R2-2208384 |
Correction on dormantBWP for RedCap in TS 38.321 |
CATT |
| R2-2208771 |
[AT119-e][114][RedCap] MAC corrections (vivo) |
vivo |
| R2-2208785 |
[AT119-e][114][RedCap] MAC corrections (vivo) – 2nd round |
vivo |
| 6.13.1 |
Organizational and Stage-2 |
|
| R2-2206934 |
LS on M6 Delay Threshold (R3-224079; contact: CATT) |
RAN3 |
| R2-2206979 |
LS on Reply LS on beam measurement reports (S5-223524; contact: Ericsson) |
SA5 |
| R2-2207472 |
Addition of SON Features Enhancement in Stage 2 |
CATT |
| R2-2208234 |
Correction to Logged MDT type handling |
Nokia, Nokia Shanghai Bell |
| R2-2208539 |
CR to 38300 on SHR and RACH optimization |
ZTE Corporation, Sanechips |
| R2-2209051 |
Summary on email discussion [AT119e][822][R17 SONMDT] Stage2 correction (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2209052 |
Correction to Rel-17 SON features |
Nokia, Nokia Shanghai Bell, CATT, Huawei, vivo, ZTE |
| R2-2209107 |
Reply LS on the user consent for trace reporting (R3-225250; contact: Nokia) |
RAN3 |
| R2-2209135 |
Reply LS on beam measurement reports (R3-225273; contact: Ericsson) |
RAN3 |
| 6.13.3 |
SON Corrections |
|
| R2-2207156 |
Correction on RACH Optimization for 2-step RA |
vivo |
| R2-2207473 |
[C321] Correction on SHR Configuration Release |
CATT |
| R2-2207474 |
[C315] [C328] Clarification on Neighbour Cell Measurement |
CATT |
| R2-2207945 |
Discussion on logging of PSCell information in MHI |
Huawei, HiSilicon |
| R2-2207946 |
Introduction of SHR in TS 38.300 |
Huawei, HiSilicon |
| R2-2207947 |
Corrections to TS 38.331 on SON and MDT |
Huawei, HiSilicon |
| R2-2208166 |
Correction to time with no PSCell in mobility history information reporting |
Ericsson |
| R2-2208167 |
PSCell information storing in Mobility History Information [E120, E121, E122] |
Ericsson, Qualcomm, CMCC, CATT |
| R2-2208168 |
Corrections to the RLF-Report for the case of RLF in the CHO recovery cell |
Ericsson |
| R2-2208235 |
Avoidance of too premature successHO-Config release |
Nokia, Nokia Shanghai Bell |
| R2-2208236 |
Correction on MHI setting upon UEInformationRequest |
Nokia, Nokia Shanghai Bell |
| R2-2208929 |
[Pre119-e][R17 SONMDT] Pre-meeting summary of 6.13.3 (Ericsson) |
Ericsson |
| R2-2209022 |
RRC Correction for SON MDT |
Ericsson, Huawei |
| R2-2209023 |
[AT117e][801] Total RAN delay calculation (Ericsson) |
Ericsson |
| 6.13.4 |
MDT Corrections |
|
| R2-2207475 |
Corrections on MDT Aspect |
CATT |
| R2-2207948 |
Discussion on capturing L2M agreements in TS 38.314 |
Huawei, HiSilicon |
| R2-2208165 |
Total RAN Delay calculation |
Ericsson |
| R2-2208206 |
Total RAN Delay calculation |
Ericsson |
| R2-2208237 |
Correction on IDC logging |
Nokia, Nokia Shanghai Bell |
| R2-2208540 |
CR to 38331 on multiple CEF report |
ZTE Corporation, Sanechips |
| R2-2208541 |
Remianing issues on multiple CEF report |
ZTE Corporation, Sanechips |
| R2-2208921 |
Pre-meeting summary of 6.13.4 |
Huawei |
| 6.14.1 |
Organizational |
|
| R2-2206906 |
Reply LS on UE capabilities for NR QoE (C1-224008; contact: Apple) |
CT1 |
| R2-2206908 |
Reply LS on NR QoE (C1-224182; contact: Huawei) |
CT1 |
| R2-2206978 |
LS Reply on QoE configuration and reporting related issues (S5-223518; contact: Ericsson) |
SA5 |
| R2-2208627 |
38.300 CR Correction for Introduction of QoE measurements in NR |
China Unicom, Huawei, HiSilicon |
| R2-2208735 |
Report of [AT119-e][250][R17 QoE] Stage-2 corrections to Rel-17 QoE (China Unicom) |
China Unicom |
| R2-2208736 |
38.300 CR Correction for Introduction of QoE measurements in NR |
China Unicom, Huawei, HiSilicon |
| R2-2209199 |
Reply LS on questions on RAN visible QoE (S4-221129; contact: Huawei) |
SA4 |
| R2-2209254 |
Stage-2 corrections to Rel-17 QoE |
China Unicom, Huawei, HiSilicon, Ericsson, Samsung, Nokia, Nokia Shanghai Bell |
| 6.14.2 |
Corrections |
|
| R2-2207425 |
Clarification of CAPC for SRB4 |
Apple |
| R2-2207426 |
Clarification of QoE Reporting with Session Start/Stop Information |
Apple |
| R2-2207530 |
Discussion on application layer measurement reporting procedure and AT commands for NR QoE |
Lenovo |
| R2-2207531 |
Corrections to application layer measurement reporting procedure |
Lenovo |
| R2-2207722 |
Correction CR for QoE measurements |
Ericsson, Huawei |
| R2-2207723 |
Correction CR for QoE measurements |
Ericsson |
| R2-2207734 |
Correction on QoE configuration and reporting |
Qualcomm Incorporated |
| R2-2207821 |
Correction on TS 38.331 for QoE |
CATT |
| R2-2207949 |
Correction to the application layer measurement configuration |
Huawei, HiSilicon |
| R2-2207950 |
Correction to the transmission of appLayerSessionStatus when pause is enabled |
Huawei, HiSilicon, China Unicom |
| R2-2208238 |
Correction to storage of application layer measurements during Pause |
Nokia, Nokia Shanghai Bell |
| R2-2208239 |
Correction to paused reporting of the application layer measurements |
Nokia, Nokia Shanghai Bell |
| R2-2208393 |
Correction on MeasurementReportAppLayer message per measConfigAppLayerId |
Samsung |
| R2-2208394 |
Correction on QoE report only including measConfigAppLayerId |
Samsung |
| R2-2208479 |
Correction on MeasurementReportAppLayer retransmission |
Google Inc. |
| R2-2208547 |
CR to 38300 on RRC segmentation |
ZTE Corporation, Sanechips, China Unicom |
| R2-2208737 |
Report of [AT119-e][251][R17 QoE] NR RRC corrections to Rel-17 QoE (Ericsson) |
Ericsson |
| R2-2208738 |
Correction CR for QoE measurements |
Ericsson, Huawei |
| R2-2208746 |
Report of [AT119-e][252][QoE] Draft CRs for QoE report handling without segmentation (Lenovo) |
Lenovo |
| R2-2208747 |
Draft CR on QoE report handling without segmentation |
Lenovo |
| R2-2209242 |
Correction CR for QoE Measurement Collection in NR |
Ericsson, China Unicom, Huawei, HiSilicon, Apple, Samsung, Google Inc. |
| 6.15.1 |
Organizational |
|
| R2-2206915 |
Reply LS on the inter-UE coordination mechanism (R1-2205400; contact: vivo) |
RAN1 |
| R2-2209123 |
Reply LS to RAN2 on RRC parameters for IUC Scheme 1 and default CBR configuration (R1-2208090; contact: Huawei) |
RAN1 |
| R2-2209124 |
Reply LS on power-saving resource allocation with absent sl-AllowedResourceSelectionConfig (R1-2208097; contact: vivo) |
RAN1 |
| R2-2209126 |
LS on SL P0 parameters (R1-2208121; contact: vivo) |
RAN1 |
| R2-2209127 |
Reply LS to RAN2 on Missing RRC Parameter in IUC Scheme 2 (R1-2208123; contact: Apple) |
RAN1 |
| R2-2209186 |
Reply LS to RAN2 on Tx profile (S2-2207033; contact: vivo) |
SA2 |
| R2-2209206 |
LS on setting RRC establishment cause value when relay UE has its own service (C1-225453; contact: vivo) |
CT1 |
| 6.15.2 |
Stage 2 corrections |
|
| R2-2207175 |
Correction on TX profile |
Xiaomi |
| R2-2208220 |
Sidelink enhancement stage 2 corrections |
Nokia, Nokia Shanghai Bell |
| R2-2208257 |
Correction on SL DRX for SL discovery |
Samsung |
| R2-2208845 |
38.300 corrections for sidelink enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2208846 |
Report of [AT119-e][505][V2X/SL] 38.300 corrections |
Nokia (Rapporteur) |
| R2-2208865 |
38.300 corrections for sidelink enhancements |
Nokia, Nokia Shanghai Bell, Samsung, Xiaomi |
| 6.15.3 |
Control plane corrections |
|
| R2-2207016 |
Correction for SL DRX |
OPPO |
| R2-2207017 |
Discussion on left issues on control plane procedure |
OPPO |
| R2-2207172 |
Removal of three priority parameters in SL-InterUE-CoordinationConfig |
NEC Corporation |
| R2-2207213 |
Corrections on RRC for SL enhancements |
ZTE Corporation, Sanechips |
| R2-2207216 |
Discussion on SL DRX remaining issues |
ZTE Corporation, Sanechips |
| R2-2207250 |
Remaing issues on power saving resource allocation |
Ericsson |
| R2-2207251 |
Corrections of 38.331 on RRCReconfigurationCompleteSidelink |
Ericsson |
| R2-2207281 |
Error handling on PC5 |
MediaTek Inc. |
| R2-2207456 |
Discussion on missing RRC parameter in IUC Scheme 2 |
Apple |
| R2-2207523 |
Corrections on the reception of RRCReconfigurationSidelink message |
CATT |
| R2-2207524 |
Corrections on the transmission of SidelinkUEInformationNR message |
CATT |
| R2-2207587 |
Corrections of 38.331 on RRCReconfigurationCompleteSidelink |
Ericsson |
| R2-2207668 |
On corrections to transmission procedures using exceptional pool for NR SL communication and NR SL discovery |
vivo |
| R2-2207669 |
On power-saving resource allocation for NR SL communication transmission and NR SL discovery transmission |
vivo |
| R2-2207760 |
Miscellaneous corrections on TS 38.331 for NR sidelink |
Xiaomi |
| R2-2207887 |
Correction on SL DRX behaviour for unicast link establishment |
Lenovo |
| R2-2207970 |
Open issues for IUC |
Intel Corporation |
| R2-2208053 |
Miscellaneous corrections on TS 38.331 for SL enhancements |
Huawei, HiSilicon |
| R2-2208056 |
Consideration on active time during unicast connection establishment |
Huawei, HiSilicon |
| R2-2208283 |
Control plane correction on NR Sidelink enhancements |
LG Electronics France |
| R2-2208598 |
Discussion and draft Reply LS to RAN1 on priority for IUC information |
vivo |
| R2-2208692 |
Corrections of 38.331 on RRCReconfigurationCompleteSidelink |
Ericsson |
| R2-2208847 |
Reply LS to RAN1 on priority for IUC |
RAN2 |
| R2-2208849 |
LS on missing RRC parameter in IUC Scheme 2 |
RAN2 |
| R2-2208850 |
Miscellaneous corrections on TS 38.331 for SL enhancements |
Huawei, HiSilicon |
| R2-2208851 |
Summary of [AT119-e][508][V2X/SL] 38.331 corrections (Huawei) |
Huawei |
| R2-2208852 |
Correction for power-saving resource allocation |
OPPO |
| R2-2208853 |
LS on TX profile |
RAN2 |
| R2-2208854 |
Correction on active time |
OPPO |
| R2-2208855 |
Summary of [AT119-e][509][V2X/SL] CP discussion (OPPO) |
OPPO |
| R2-2208866 |
Correction for power-saving resource allocation |
OPPO |
| R2-2208867 |
LS on Per-FS L1 feature for NR sidelink discovery BC-list |
RAN2 |
| R2-2208869 |
Miscellaneous corrections on TS 38.331 for SL enhancements |
Huawei, HiSilicon (Rapporteur) |
| R2-2208901 |
Discussion on left issues on UE capability |
OPPO |
| R2-2208953 |
Reply LS to RAN1 on priority for IUC |
RAN2 |
| R2-2209267 |
Correction for power-saving resource allocation |
OPPO |
| 6.15.4 |
User plane corrections |
|
| R2-2206984 |
Correction on IUC for resource re-selection in re-evaluation and pre-emption |
SHARP Corporation |
| R2-2206985 |
Correction on resource re-selection for non-preferred resource set |
SHARP Corporation |
| R2-2207029 |
Discussion on left issues on user plane procedure |
OPPO |
| R2-2207030 |
Correction on user plane aspects |
OPPO |
| R2-2207174 |
Discussion on retransmission issue |
Xiaomi |
| R2-2207183 |
Correction on SL grant selection procedure |
NEC Corporation |
| R2-2207214 |
Correction on MAC for SL enhancement |
ZTE Corporation, Sanechips |
| R2-2207215 |
Discussion on inter-UE coordination |
ZTE Corporation, Sanechips |
| R2-2207248 |
Impact of IUC inofmation on LCP |
Ericsson |
| R2-2207249 |
Configuration aspects of SL DRX |
Ericsson |
| R2-2207454 |
Correction on TX Pool Selection for Inter-UE Coordination |
Apple |
| R2-2207455 |
Clarification on destination selection for Inter-UE Coordination |
Apple |
| R2-2207525 |
UP Leftover Issues on SL DRX |
CATT |
| R2-2207526 |
Open Issues of Inter-UE Coordination |
CATT |
| R2-2207759 |
Miscellaneous corrections on TS 38.321 for NR sidelink |
Xiaomi |
| R2-2207850 |
Correction for Sidelink DRX |
Sharp |
| R2-2207851 |
Correction for Sidelink DRX |
Sharp |
| R2-2207890 |
LCP impacts for SL inter-UE coordination |
Lenovo |
| R2-2208054 |
Correction on inter-UE coordination |
Huawei, HiSilicon |
| R2-2208055 |
Clarification on Uu DRX for SL communication |
Huawei, HiSilicon |
| R2-2208057 |
Correction on sl-drx-inactivityTimer and LCP for discovery |
Huawei, HiSilicon |
| R2-2208148 |
HARQ RTT for pools without PSFCH |
InterDigital |
| R2-2208149 |
SR Configuration for SL DRX Command |
InterDigital |
| R2-2208150 |
UL/SL Prioritization for SL Relay |
InterDigital |
| R2-2208183 |
Open issue on SL-DRX |
Intel Corporation |
| R2-2208222 |
Further considerations on sidelink IUC scheme 2 |
Nokia, Nokia Shanghai Bell |
| R2-2208258 |
Correction on SL grant (re)selection based on sl-interUE-CoordinationSchemeN |
Samsung |
| R2-2208281 |
User plane corrections on NR Sidelink enhancements |
LG Electronics France |
| R2-2208365 |
Correction on DRX timers for SL |
ASUSTeK |
| R2-2208513 |
Correction to inter-UE coordination information triggered by a condition |
Qualcomm India Pvt Ltd |
| R2-2208549 |
Corrections on SL DRX operation |
ASUSTEK COMPUTER (SHANGHAI) |
| R2-2208599 |
Correction on UE behavior in LCP considering PSFCH reception capability |
vivo |
| R2-2208602 |
Remaining issues for Inter-UE coordination procedure |
vivo |
| R2-2208605 |
Down selection of SR configuration for SL DRX MAC Command CE |
Nokia, Nokia Shanghai Bell |
| R2-2208856 |
38.321 corrections for SL enhancement |
LG Electronics |
| R2-2208857 |
Summary of [AT119-e][510][V2X/SL] 38.321 corrections (Huawei) |
LG |
| R2-2208858 |
Correction on user plane aspects |
OPPO |
| R2-2208859 |
Summary of [AT119-e][511][V2X/SL] UP discussion(OPPO) |
OPPO |
| R2-2208868 |
38.321 corrections for SL enhancement |
LG |
| R2-2208994 |
38.321 corrections for SL enhancement |
LG Electronics |
| 6.16 |
NR Non-Public Network enhancements |
|
| R2-2207163 |
CR on the ims-EmergencySupport for the SNPN and PLMN RAN sharing scenario |
ZTE Corporation, Sanechips |
| R2-2207501 |
Correction to 38.300 on GIN |
Huawei, HiSilicon |
| R2-2208624 |
Changing the gins-PerSNPN-List Need Code |
Ericsson |
| R2-2209113 |
(reserved)Summary of [ AT119-e][027][NPN] NPN corrections (ZTE) |
ZTE Corporation, Sanechips |
| 6.17.1 |
Organizational |
|
| R2-2206926 |
LS on RAN1#109-e agreements with RAN2 impact (R1-2205591; contact: Samsung) |
RAN1 |
| R2-2209129 |
Reply LS on LS on further questions on feMIMO RRC parameters (R1-2208224; contact: Ericsson) |
RAN1 |
| R2-2209151 |
LS on TCI state indication of CORESET#0 associated with SS#0 (R1-2208203; contact: Intel, vivo) |
RAN1 |
| R2-2209171 |
LS on active TCI state list for UL TCI (R4-2214972; contact: Nokia) |
RAN4 |
| 6.17.2 |
RRC centric Corrections |
|
| R2-2207127 |
Clarification on search space link id and others |
OPPO |
| R2-2207369 |
Correction on 38.331 for feMIMO |
Langbo |
| R2-2207733 |
Discussion on Rel-17 MIMO RRC corrections |
Ericsson |
| R2-2207773 |
Miscellaneous RRC corrections for feMIMO |
CATT |
| R2-2207810 |
Clarification on the initial state of BFD RS |
Xiaomi |
| R2-2207923 |
Corrections for Release-17 feMIMO |
Ericsson |
| R2-2208557 |
CR on 38.331 for TCI-state |
ZTE Corporation,Sanechips |
| R2-2208558 |
CR on 38.331 for TCI-UL-state |
ZTE Corporation,Sanechips |
| R2-2208652 |
FeMIMO RRC corrections |
Huawei, HiSilicon |
| R2-2208906 |
[Pre119-e][002][feMIMO] RRC centric summary (Ericsson) |
Ericsson |
| R2-2208963 |
[DRAFT] LS on further questions on feMIMO RRC parameters |
Ericsson |
| R2-2208964 |
LS on further questions on feMIMO RRC parameters |
RAN2 |
| R2-2209040 |
[AT119-e][002][feMIMO] RRC centric (Ericsson) |
Ericsson |
| R2-2209233 |
Corrections for Release-17 feMIMO |
Ericsson |
| R2-2209258 |
Corrections for Release-17 feMIMO |
Ericsson |
| 6.17.3 |
MAC centric Corrections |
|
| R2-2207364 |
BFD-RS set specific BFI_COUNTER resetting |
Langbo |
| R2-2207365 |
Correction on 38.321 for feMIMO |
Langbo |
| R2-2207405 |
Correction to BFI_COUNTER reset |
Fujitsu |
| R2-2207570 |
CR for correction on PH selection |
LG Electronics Inc. |
| R2-2207731 |
Corrections for Release-17 feMIMO |
Ericsson |
| R2-2207774 |
Miscellaneous MAC corrections for feMIMO |
CATT |
| R2-2207809 |
Clarification on the deactivated SCell of the unified TCI-state |
Xiaomi |
| R2-2208018 |
Remaining issues on PHR for FeMIMO |
Nokia, Nokia Shanghai Bell |
| R2-2208114 |
Remaining issues of feMIMO MAC |
Qualcomm Incorporated |
| R2-2208366 |
Corrections on Unified TCI States Activation/Deactivation MAC CE |
ASUSTeK |
| R2-2208526 |
Miscellaneous MAC Corrections on feMIMO |
Samsung |
| R2-2208527 |
Handling of BFD-RS Set Configuration and Activation |
Samsung |
| R2-2208653 |
Corrections to FeMIMO MAC |
Huawei, HiSilicon |
| R2-2208923 |
[Pre119-e][001][feMIMO] MAC centric summary – focus on initial topic (Samsung |
Samsung |
| R2-2209020 |
Report of [AT119-e][001][feMIMO] MAC centric (Samsung) |
Samsung |
| R2-2209021 |
Miscellaneous MAC Corrections on feMIMO |
Samsung |
| R2-2209248 |
Miscellaneous MAC Corrections on feMIMO |
Samsung |
| 6.18.1 |
Common signalling framework |
|
| R2-2207679 |
Miscellaneous corrections to slice-specific RACH configuration |
Spreadtrum Communications |
| R2-2207820 |
Correction on TS 38 331 for RACH common |
CATT |
| R2-2207981 |
Correction on startPreambleForThisPartition |
ZTE Corporation, Sanechips, Ericsson |
| R2-2207982 |
Configuration of preambles for feature combination |
ZTE Corporation, Sanechips |
| R2-2207989 |
RRC corrections to common RACH framework |
Huawei, HiSilicon |
| R2-2207997 |
On the number of RACH partitions |
MediaTek Inc. |
| R2-2208240 |
Miscellaneous corrections to common signalling for RACH partitioning |
Nokia, Nokia Shanghai Bell |
| R2-2208399 |
Correction on Feature Combination |
LG Electronics Inc. |
| R2-2208910 |
Correction on the featurePriorities |
Huawei, HiSilicon |
| R2-2208995 |
Summary of [AT119-e][307][RA Part] CP open issues and CR 38.331 (Ericsson) |
Ericsson |
| R2-2208996 |
Correction for features applicable for common signalling for RACH Partitioning |
Ericsson |
| 6.18.2 |
Common aspects of RACH procedure |
|
| R2-2207905 |
UL carrier selection for RA-SDT |
Nokia, Nokia Shanghai Bell |
| R2-2207990 |
MAC correction to the RACH partitioning |
Huawei, HiSilicon |
| R2-2208131 |
Correction to CFRA with additionalRACH-Configs |
Ericsson |
| R2-2208132 |
Correction to CFRA with additionalRACH-Configs |
Ericsson |
| R2-2208400 |
Correction on fallback cases from CFRA to CBRA in CE-only BWP |
LG Electronics Inc. |
| R2-2208614 |
38.321 CR Correction on the provision of the feature applicability for RACH |
Beijing Xiaomi Software Tech |
| R2-2208662 |
Correction on RO Selection with RA Partitioning |
vivo |
| R2-2208916 |
Correction on RO Selection with RA Partitioning |
vivo |
| R2-2208988 |
Report of [AT119-e][308][RA Part] UP open issues and CR 38.321 (ZTE) |
ZTE Corporation (rapporteur) |
| R2-2209093 |
Correction on RO Selection with RA Partitioning |
vivo, Xiaomi, ZTE Corporation (rapporteur) |
| 6.19.1 |
Organizational |
|
| R2-2206960 |
Reply LS to RAN1/RAN2 on DMRS bundling (R4-2211225; contact: MediaTek) |
RAN4 |
| R2-2207891 |
Miscellaneous corrections to NR coverage enhancements |
Huawei, HiSilicon, China Telecom, ZTE Corporation |
| R2-2208768 |
Miscellaneous corrections to NR coverage enhancements |
Huawei, HiSilicon, China Telecom, ZTE Corporation, Ericsson |
| 6.19.2 |
General |
|
| R2-2207130 |
Discussion on Capability of DMRS Bundling |
vivo |
| R2-2207132 |
Clarification on only CE RACH Resources |
vivo |
| R2-2208184 |
Correction of need codes and field descriptions for DMRS bundling |
Ericsson |
| 6.20.1 |
Organizational |
|
| R2-2206913 |
LS to RAN2 on RRC parameter updates for NR up to 71GHz (R1-2205380; contact: Qualcomm) |
RAN1 |
| R2-2206925 |
LS on TCI assumption for RSSI measurement for FR2-2 (R1-2205582; contact: Qualcomm) |
RAN1 |
| R2-2206956 |
LS on CCA configurations of neighbour cells (R4-2211171; contact: Nokia) |
RAN4 |
| R2-2207256 |
Correction of RRC CR for 71 GHz |
Ericsson |
| R2-2207985 |
Discussion on CCA configuration of neighbour cell |
ZTE Corporation, Sanechips |
| R2-2209121 |
LS to RAN2 on RRC parameter impact for NR up to 71GHz (R1-2208040; contact: vivo) |
RAN1 |
| R2-2209153 |
LS on condition to apply channel access procedure (R1-2208231; contact: OPPO) |
RAN1 |
| R2-2209163 |
LS reply on TCI assumption for RSSI measurement for FR2-2 (R4-2214477; contact: Apple) |
RAN4 |
| 6.20.2 |
Control plane corrections |
|
| R2-2207253 |
Corrections of UE Capabilityíes for FR2-2 |
Ericsson |
| R2-2207254 |
discussion on RAN4 LS R4-2211171 |
Ericsson |
| R2-2207255 |
Discussion the need of BWP index for L3 RSSI measurement configuration |
Ericsson |
| R2-2207460 |
Discussion on CCA configurations of neighbour cells in FR2-2 |
Apple |
| R2-2207461 |
[Draft] LS Reply on CCA configurations of neighbour cells in FR2-2 |
Apple |
| R2-2207543 |
CCA information for neighbour cells |
Nokia, Nokia Shanghai Bell |
| R2-2207544 |
CCA information for neighbour cells |
Nokia, Nokia Shanghai Bell |
| R2-2207959 |
Release FR2-2 related preference indication configurations in RRC connection reestablishment |
Google Inc. |
| R2-2207983 |
CSI-RS related issues for NR operation above 71 GHz |
ZTE Corporation, Sanechips |
| R2-2207984 |
Inter-RAT measurement issues for NR operation above 71 GHz |
ZTE Corporation, Sanechips |
| R2-2208063 |
Discussion on RSSI measurement issues for FR2-2 |
Huawei, HiSilicon |
| R2-2208064 |
Correction to PO configuration for FR2-2 |
Huawei, HiSilicon |
| R2-2208065 |
Discussion on the LS on the CCA configuration of neighbour cell |
Huawei, HiSilicon |
| R2-2208252 |
Channel Access Mode for Neighbor Cells |
Qualcomm Incorporated |
| R2-2208515 |
Discussion on a defalut value of duration-r17 for SCS 480 kHz and 960 kHz |
LG Electronics Inc. |
| R2-2208516 |
Correction on duration-r17 for SCS 480 KHz and 960 KHz |
LG Electronics Inc. |
| R2-2208693 |
Correction of RRC CR for 71 GHz |
Ericsson |
| R2-2208739 |
Report of [AT119-e][210][71 GHz] RRC corrections to 71 GHz (Ericsson) |
Ericsson |
| R2-2208740 |
Correction of RRC CR for 71 GHz |
Ericsson |
| R2-2208741 |
Report of [AT119-e][211][71 GHz] CCA for neighbour cells (Nokia) |
Nokia |
| R2-2208742 |
[Draft] LS Reply on CCA configurations of neighbour cells in FR2-2 |
Nokia |
| R2-2208743 |
Report of [AT119-e][212][71 GHz] HO from E-UTRA to FR2-2 (ZTE) |
ZTE |
| R2-2208744 |
RRC CR for HO from E-UTRA to FR2-2 |
ZTE |
| R2-2208745 |
UE Capability CR for HO from E-UTRA to FR2-2 |
ZTE |
| R2-2209009 |
CCA information for neighbour cells |
Nokia, Nokia Shanghai Bell |
| R2-2209079 |
FR2-2 and CCA configuration |
Nokia, Nokia Shanghai Bell |
| R2-2209101 |
MeasConfig corrections for above 71 GHz operation |
ZTE Corporation, Sanechips |
| R2-2209210 |
MeasConfig corrections for above 71 GHz operation |
ZTE Corporation, Sanechips |
| R2-2209212 |
Correction on RRC for 71GHz |
Ericsson |
| R2-2209234 |
FR2-2 and CCA configuration |
Nokia, Nokia Shanghai Bell |
| R2-2209235 |
Reply LS on CCA configurations of neighbour cells |
RAN2 |
| R2-2209249 |
MeasConfig corrections for above 71 GHz operation |
ZTE Corporation, Sanechips |
| R2-2209250 |
UE Capability CR for HO from E-UTRA to FR2-2 |
ZTE Corporation, Sanechips |
| 6.21.1 |
TEI proposals |
|
| R2-2206904 |
Reply LS on EPS fallback enhancements (C1-223535; contact: Qualcomm) |
CT1 |
| R2-2206954 |
LS on timing advance (TADV) report mapping for NR UL E-CID positioning (R4-2211167; contact: Ericsson) |
RAN4 |
| R2-2206958 |
LS on Incorrect PMI Reporting (R4-2211204; contact: Apple) |
RAN4 |
| R2-2206974 |
Reply LS on EPS fallback enhancements (S3-221162; contact: Ericsson) |
SA3 |
| R2-2207434 |
SDAP end-marker in RLC UM |
Apple, Futurewei, Spreadtrum, FGI, Asia Pacific Telecom, T-Mobile USA, ZTE Corporation |
| R2-2207938 |
Priority based inter-freq measurement reporting |
Apple |
| R2-2208241 |
Inclusion of the CSI reports in MDT framework |
Nokia, Nokia Shanghai Bell, Deutsche Telekom, Verizon |
| R2-2208430 |
Discussion on remote access issue |
CMCC, vivo, Huawei |
| R2-2208617 |
Enhancements for emergency services fallback handling |
Huawei, HiSilicon, CMCC, China Telecom, China Unicom, Telecom Italia |
| R2-2208668 |
Correction to DRX operation with bundling controlled in the DCI |
Ericsson, Nokia, T-Mobile USA, Verizon, Docomo |
| R2-2208918 |
Start drx-HARQ-RTT-TimerUL after last repetition [ulHARQ_RTT_Timer] |
Ericsson, Nokia |
| R2-2208919 |
Start drx-HARQ-RTT-TimerUL after last repetition [ulHARQ_RTT_Timer] |
Ericsson, Nokia |
| R2-2208920 |
Start drx-HARQ-RTT-TimerUL after last repetition [ulHARQ_RTT_Timer] |
Ericsson, Nokia |
| R2-2209106 |
Reply LS on Flexible Global RAN Node ID (R3-225248; contact: Ericsson) |
RAN3 |
| R2-2209112 |
Comments on New proposals |
Chair (Mediatek inc) |
| R2-2209116 |
Report of [AT119-e][037][NRTEI17] Emergency Service Enhancement (Huawei) |
Huawei, HiSilicon |
| R2-2209218 |
Report of [Post119-e][037][NRTEI17] Emergency Service Enhancement |
Huawei |
| 6.21.2 |
Corrections |
|
| R2-2207529 |
Corrections to the description of gNB ID length reporting capabilities [gNB_ID_Length] |
Lenovo |
| R2-2207607 |
Early measurement for EPS Fallback |
vivo |
| R2-2207608 |
38331 CR for Early measurement for EPS Fallback |
vivo |
| R2-2207609 |
38306 CR for Early measurement for EPS Fallback |
vivo |
| R2-2207610 |
LS to RAN4 on idle_inactive measurement for EPS Fallback |
vivo |
| R2-2208372 |
Corrections on mpsPriorityIndication |
Huawei, HiSilicon |
| R2-2208483 |
Clarification on NR sidelink relay related configuration |
Huawei, HiSilicon |
| R2-2208999 |
Report of [AT119-e][020][NR17] TEI Corrections |
vivo |
| R2-2209000 |
LS to RAN4 on idle/inactive measurement for EPS Fallback |
RAN2 |
| R2-2209033 |
Correction on mpsPriorityIndication |
Huawei, HiSilicon |
| R2-2209034 |
Correction on mpsPriorityIndication |
Huawei, HiSilicon |
| R2-2209035 |
Correction on mpsPriorityIndication |
Huawei, HiSilicon |
| R2-2209036 |
Correction on mpsPriorityIndication |
Huawei, HiSilicon |
| R2-2209219 |
38306 CR for Early measurement for EPS Fallback [IdleMeaEPSFB] |
vivo |
| R2-2209272 |
Correction on mpsPriorityIndication |
Huawei, HiSilicon |
| 6.22 |
NR and MR-DC measurement gap enhancements |
|
| R2-2206939 |
LS on R17 NR MG enhancements – Pre-configured MG (R4-2210587; contact: OPPO, Intel) |
RAN4 |
| R2-2206940 |
LS on R17 MG enhancement - NCSG (R4-2210589; contact: Apple) |
RAN4 |
| R2-2206999 |
Response LS on RRC-based Pre-MG (de)activation on BWP#0 |
OPPO |
| R2-2207000 |
Discussion on RRC-based Pre-MG (de)activation on BWP#0 |
OPPO |
| R2-2207145 |
Discussion on pre-configured MG for BWP#0 |
Huawei, HiSilicon |
| R2-2207146 |
Correction on NCSG pattern |
Huawei, HiSilicon |
| R2-2207895 |
Gap coordination for MR-DC |
Google Inc. |
| R2-2208105 |
Correction on pre-configured gap activation and deactivation |
ZTE Corporation, Sanechips |
| R2-2208106 |
Correction on mgta configuration |
ZTE Corporation, Sanechips |
| R2-2208464 |
Remaining Issues for MGE Configurations |
MediaTek Inc. |
| R2-2208471 |
Remaining Issues on MGE Capabilities |
MediaTek Inc. |
| R2-2208562 |
Clarification on associatedMeasGapSSB for concurrent MG |
Nokia, Nokia Shanghai Bell |
| R2-2209030 |
Report of [AT119-e][033][MGE] (MediaTek) |
MediaTek |
| R2-2209031 |
Correction on measurement gap enhancement configurations |
MediaTek Inc. |
| R2-2209032 |
Correction on measurement gap enhancement capabilities |
MediaTek Inc. |
| R2-2209157 |
LS on UE capability indicating the support of deriveSSB-IndexFromCell-inter (R4-2214337; contact: Huawei) |
RAN4 |
| R2-2209172 |
LS on priority for legacy gaps (R4-2215132; contact: Nokia) |
RAN4 |
| 6.23 |
Uplink Data Compression (UDC) |
|
| R2-2207940 |
Discussion on UE behaviour about UDC in RRC resume procedure |
Huawei, HiSilicon |
| R2-2208205 |
Removal of UDC in the description of Data field |
Lenovo |
| R2-2208587 |
Clarification on UDC packet |
Samsung |
| R2-2208971 |
Correction on UE behaviour about UDC in RRC resume procedure |
Huawei, HiSilicon, China Telecom, CATT |
| R2-2209004 |
Offline 21: UDC Correction |
Samsung |
| 6.24.1 |
RAN4 led Items |
|
| R2-2206920 |
Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure (R1-2205463; contact: Huawei) |
RAN1 |
| R2-2206936 |
LS on release independent for FR1 HST RRM enhancement (R4-2206846; contact: CMCC) |
RAN4 |
| R2-2206937 |
LS on release independent for FR1 HST demodulation (R4-2207195; contact: CMCC) |
RAN4 |
| R2-2206951 |
LS on DC location for intra-band CA (R4-2210782; contact: vivo) |
RAN4 |
| R2-2206955 |
LS on clarification of RACH prioritisation rules between LTE and NR-U (R4-2211170; contact: Ericsson) |
RAN4 |
| R2-2206959 |
LS to RAN2 on UL gap in FR2 RF enhancement (R4-2211222; contact: Apple) |
RAN4 |
| R2-2207135 |
Discussion on DC location for more than 2 UL CCs |
OPPO |
| R2-2207136 |
CR on UE capability for DC location for more than 2 UL CCs |
OPPO |
| R2-2207138 |
CR on DC location for more than 2 UL CCs |
OPPO |
| R2-2207333 |
Switching option capability for UL 2Tx-2Tx switching |
Qualcomm Incorporated, ZTE Corporation, Nokia, Nokia Shanghai Bell, OPPO, MediaTek Inc., Xiaomi Communications, Ericsson |
| R2-2207334 |
Introduction of switching option UE capability for UL 2Tx-2Tx switching |
Qualcomm Incorporated, ZTE Corporation, Nokia, Nokia Shanghai Bell, OPPO, MediaTek Inc., Xiaomi Communications, Ericsson |
| R2-2207335 |
Introduction of switching option UE capability for UL 2Tx-2Tx switching |
Qualcomm Incorporated, ZTE Corporation, Nokia, Nokia Shanghai Bell, OPPO, MediaTek Inc., Xiaomi Communications, Ericsson |
| R2-2207613 |
Remaining issues on DC location report for Rel-17 |
vivo |
| R2-2207614 |
LS to RAN4 on DC location |
vivo |
| R2-2207856 |
Correction for Rel-17 CRS interference mitigation |
Sharp |
| R2-2207973 |
Reply LS on release independence aspects of newly introduced FR2 CA BW Classes and CBM/IBM UE capability |
Nokia, Nokia Shanghai Bell |
| R2-2207974 |
Introduction of FR2 FBG2 CA BW classes |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips, Qualcomm, Xiaomi Communications |
| R2-2207975 |
Introduction of FR2 FBG2 CA BW classes |
Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson, ZTE Corporation, Sanechips, Qualcomm, Xiaomi Communications |
| R2-2208370 |
Discussion on the update to endorsed CRs for DC location report for more than 2CC |
Huawei, HiSilicon |
| R2-2208371 |
Introduction of DC location reporting for more than 2CCs |
Huawei, HiSilicon |
| R2-2208480 |
Discussion on supporting 2Tx-2Tx switching for Rel-17 capability reporting |
Huawei, HiSilicon, CMCC, China Unicom, CATT |
| R2-2208510 |
Discussion on FR2 new bandwidth classes |
Huawei, HiSilicon |
| R2-2208511 |
Introduction of FR2 FBG5 CA BW classes |
Huawei, HiSilicon |
| R2-2208611 |
Discussion on UE capability reporting for Rel-17 UL Tx switching enhancement |
CTSI |
| R2-2208931 |
Correction on FR2 UL gap |
Apple |
| R2-2208968 |
CR on UE capability for DC location for more than 2 UL CCs |
OPPO |
| R2-2208981 |
CR on DC location for more than 2 UL CCs |
OPPO |
| R2-2209001 |
Summary for email discussion [AT119-e][022][NR17] DC Location Report (vivo) |
vivo |
| R2-2209002 |
LS to RAN4 on DC location |
RAN2 |
| R2-2209037 |
Introduction of switching option UE capability for UL 2Tx-2Tx switching |
Qualcomm Incorporated, ZTE Corporation, Nokia, Nokia Shanghai Bell, OPPO, MediaTek Inc., Xiaomi Communications, Ericsson |
| R2-2209038 |
Introduction of switching option UE capability for UL 2Tx-2Tx switching |
Qualcomm Incorporated, ZTE Corporation, Nokia, Nokia Shanghai Bell, OPPO, MediaTek Inc., Xiaomi Communications, Ericsson |
| R2-2209039 |
LS on switching option capability for UL 2Tx-2Tx switching |
Qualcomm Incorporated |
| R2-2209054 |
LS on CRS-IM network assistance signalling (R4-2214362; contact: Qualcomm) |
RAN4 |
| R2-2209080 |
Introduction of DC location report for more than 2CCs |
Huawei, HiSilicon |
| R2-2209082 |
Report of [AT119-e][023][NR17] FR2 BW classes (Nokia) |
Nokia, Nokia Shanghai Bell |
| R2-2209083 |
Summary of [AT119-e][030][NR17] FR2 UL Gap MAC CR (Apple) |
Apple |
| R2-2209084 |
Correction on FR2 UL gap |
Apple |
| R2-2209111 |
LS on switching option capability for UL 2Tx-2Tx switching |
RAN2 |
| R2-2209119 |
Reply LS on clarification of RACH prioritisation rules between LTE and NR-U (R1-2207935; contact: Ericsson) |
RAN1 |
| R2-2209159 |
LS on intra-band UL CA DC default location clarification (R4-2214419; contact: Apple) |
RAN4 |
| R2-2209169 |
Reply LS on clarification of dualPA-Architecture capability (R4-2214924; contact: Samsung) |
RAN4 |
| R2-2209174 |
LS on new contiguous BW classes for legacy networks (R4-2215160; contact: Qualcomm) |
RAN4 |
| R2-2209229 |
Corrections on CRS-IM network assistance information |
Qualcomm Incorporated |
| R2-2209230 |
Corrections on CRS-IM network assistance information |
Qualcomm Incorporated |
| R2-2209246 |
Summary of [Post119-e][046][NR17] FR2 UL Gap MAC CR (Apple) |
Apple |
| 6.24.3 |
Other |
|
| R2-2208133 |
Correction to MINT - applicableDisasterInfoList |
Ericsson |
| R2-2208982 |
Correction to MINT - applicableDisasterInfoList [MINT] |
Ericsson |
| R2-2209136 |
Correction to MINT - applicableDisasterInfoList [MINT] |
Ericsson |
| R2-2209204 |
Reply LS on system information extensions for minimization of service interruption (MINT) (C1-225386; contact: Ericsson) |
CT1 |
| R2-2209276 |
Correction to MINT - applicableDisasterInfoList [MINT] |
Ericsson |
| 7.1.1 |
Organizational and Stage-2 |
|
| R2-2206972 |
LS on updated Rel-17 RAN1 UE features list for LTE (R1-2205612; contact: NTT DOCOMO, AT&T) |
RAN1 |
| R2-2209118 |
LS on updated Rel-17 RAN1 UE features lists for LTE after RAN1#110 Thursday (R1-2207926; contact: NTT DOCOMO, AT&T) |
RAN1 |
| 7.1.2 |
Control Plane Corrections |
|
| R2-2207492 |
DRB release |
LG Electronics Inc. |
| R2-2207493 |
36.331 CR on DRB release |
LG Electronics Inc. |
| R2-2208303 |
Discussion on introducing the value infinity for the hysteresis timer |
Ericsson |
| R2-2208304 |
Introduction of value infinity for coverage based paging carrier hysteresis timer |
Ericsson |
| R2-2208305 |
Introduction of value infinity for coverage based paging carrier hysteresis timer |
Ericsson |
| R2-2208597 |
36331_(R17)_Correction on npusch-MCS field description |
ZTE Corporation, Sanechips |
| R2-2209098 |
Correction on npusch-MCS field description |
ZTE Corporation, Sanechips |
| 7.2.1 |
Organizational |
|
| R2-2206933 |
Reply LS on open issues for NB-IoT and eMTC support for NTN (R3-224007; contact: ZTE) |
RAN3 |
| R2-2206938 |
LS reply on UE capability for 16QAM for NB-IoT (R4-2210571; contact: Ericsson) |
RAN4 |
| R2-2206961 |
Reply LS on Emergency services and UE rejected with "PLMN not allowed to operate in the country of the UE’s location" (S1-221290; contact: Apple) |
SA1 |
| R2-2207153 |
Miscellaneous corrections to TS 36.331 for IoT NTN |
Huawei, HiSilicon |
| R2-2208762 |
Correction to IoT-NTN stage 2 correction description |
Ericsson |
| R2-2208781 |
Introduce "PLMNs not allowed to operate at the present UE location" in table AS/NAS functional division |
Ericsson |
| R2-2208784 |
Miscellaneous corrections to TS 36.331 for IoT NTN |
Huawei, HiSilicon |
| R2-2208789 |
UE capabilities correction for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2209041 |
Corrections for Supporting Non-Terrestrial Network in NB-IoT and eMTC |
MediaTek |
| R2-2209197 |
Reply to LS on UE capability signalling for IoT-NTN (S2-2207839; contact: Vodafone) |
SA2 |
| R2-2209262 |
Correction to IoT-NTN stage 2 correction description |
Ericsson |
| R2-2209263 |
Introduce "PLMNs not allowed to operate at the present UE location" in table AS/NAS functional division |
Ericsson |
| R2-2209264 |
UE capabilities correction for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| 7.2.2 |
User Plane |
|
| R2-2207056 |
Discussion on mac-ContentionResolutionTimer in IoT NTN |
OPPO |
| R2-2207064 |
Correction on the definition of deltaPDCCH in (UL) HARQ RTT Timer for NB-IoT NTN |
OPPO |
| R2-2207349 |
Clarification on PDCCH-based HARQ feedback |
Qualcomm Incorporated |
| R2-2207351 |
Clarification on the expiry of the contention resolution timer. |
Qualcomm Incorporated |
| R2-2207599 |
Discussion on the triggering of TA reporting |
Huawei, HiSilicon |
| R2-2207600 |
Discussion on MSG3 retransmission |
Huawei, HiSilicon |
| R2-2207817 |
36321CR_Corrections for RTToffset in HARQ RTT timers |
ZTE Corporation, Sanechips |
| R2-2207824 |
Discussion on contention resolution timer in IoT NTN |
ZTE Corporation, Sanechips |
| R2-2208387 |
Correction on TA Reporting Triggering Condition for IoT NTN in TS 36.321 |
CATT |
| R2-2208563 |
Issue on false claiming of contention resolution failure for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208664 |
R17 IoT NTN User Plane issues |
Ericsson |
| R2-2208754 |
Report of [AT119-e][104][IoT-NTN] CR timer |
ZTE (rapporteur) |
| R2-2208757 |
Report of [AT119-e][106][IoT-NTN]MAC corrections (Mediatek) |
MediaTek |
| R2-2208780 |
Report of [AT119-e][106][IoT-NTN] MAC corrections (Mediatek) |
MediaTek |
| 7.2.3 |
RRC |
|
| R2-2207057 |
Correction to RRC-MAC interaction on UL synchronisation in IoT NTN |
OPPO |
| R2-2207059 |
Discussion on segmented precompensation gap configuration in IoT NTN |
OPPO |
| R2-2207150 |
Discussion on neighbour cell ephemeris |
Huawei, HiSilicon |
| R2-2207151 |
Correction to 36.331 on neighbour cell ephemeris |
Huawei, HiSilicon |
| R2-2207152 |
Discussion on parameters for discontinuous coverage |
Huawei, HiSilicon |
| R2-2207308 |
Add TX gap parameter and capability for IoT NTN |
MediaTek Inc. |
| R2-2207309 |
Correction on IoT NTN ASN.1 |
MediaTek Inc. |
| R2-2207310 |
Specify ECI to the reference frame of orbital parameters |
MediaTek Inc. |
| R2-2207311 |
Trigger RLF when SIB31 cannot be acquired during T318 |
MediaTek Inc. |
| R2-2207350 |
Indication of Koffset update in SIB31 |
Qualcomm Incorporated |
| R2-2207353 |
RRC Release with redirection to TN |
Qualcomm Incorporated |
| R2-2207789 |
Discussion on footprint parameters in SIB32 |
ZTE Corporation, Sanechips |
| R2-2207790 |
Discussion on epochTime in SIB31 |
ZTE Corporation, Sanechips |
| R2-2207791 |
36331CR_RRC miscellaneous corrections |
ZTE Corporation, Sanechips |
| R2-2208038 |
Miscellanious corrections to RRC for for IoT-NTN |
Nokia Solutions & Networks (I) |
| R2-2208043 |
RRC changes for Gap configuration for uplink segemented tansmission in IoT-NTN |
Nokia, Nokia SHanghai Bell |
| R2-2208129 |
Miscellanious Corrections to RRC for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208294 |
Correction to coarseLocationInfo field description for IoT NTN |
Eutelsat S.A. |
| R2-2208564 |
Issue on GNSS measurement during eMTC handover |
Nokia, Nokia Shanghai Bell |
| R2-2208574 |
correction on coarselocationreq |
Xiaomi, Thales |
| R2-2208665 |
R17 IoT NTN RRC Corrections |
Ericsson |
| R2-2208681 |
NTN Configuration at CHO |
Sequans Communications |
| R2-2208682 |
RRC changes for Gap configuration for uplink segemented tansmission in IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208684 |
RRC changes for Gap configuration for uplink segemented tansmission in IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208755 |
Report of [AT119-e][105][IoT-NTN] RRC corrections (Huawei) |
Huawei, HiSilicon |
| R2-2208756 |
Report of [AT119-e][105][IoT-NTN] RRC corrections (Huawei) - Second round |
Huawei, HiSilicon |
| 7.2.4 |
Idle Inactive mode |
|
| R2-2208138 |
Correction on Measurement rules for cell re-selection for IoT NTN |
Samsung R&D Institute UK |
| R2-2208669 |
R17 IoT NTN Idle mode issues |
Ericsson |
| R2-2208758 |
Report of [AT119-e][107][IoT-NTN] Idle mode corrections (Ericsson) |
Ericsson |
| 7.2.5 |
UE capabilities |
|
| R2-2207058 |
Discussion on UE capability on segmented precompensation gap in IoT NTN |
OPPO |
| R2-2207307 |
Add TX gap capability for IoT NTN |
MediaTek Inc. |
| R2-2207352 |
Reporting the support of TN bands to NTN |
Qualcomm Incorporated |
| R2-2208044 |
New UE capability for Pre-compensation-gap for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208666 |
R17 IoT NTN UE Capabilities corrections |
Ericsson |
| R2-2208759 |
[AT119-e][108][IoT-NTN] UE capabilities (Nokia) |
Nokia |
| 7.2.6 |
Other |
|
| R2-2208667 |
R17 IoT NTN stage 2 corrections |
Ericsson |
| 8.1.1 |
Organizational |
|
| R2-2208108 |
Work plan for NR network-controlled repeaters |
ZTE Corporation (Rapporteur) |
| R2-2208109 |
TR 38.867 on network-controlled repeaters management |
ZTE Corporation (Rapporteur) |
| R2-2209053 |
Progress on NCR identification and authorization (R3-225254; contact: ZTE) |
RAN3 |
| R2-2209108 |
LS on NCR Solutions (R3-225253; contact: ZTE) |
RAN3 |
| 8.1.2 |
General |
|
| R2-2207123 |
Identification and Authorization of Network-Controlled Repeater |
Intel Corporation |
| R2-2207205 |
Identification and authorization of Network Controlled Repeater |
Nokia, Nokia Shanghai Bell |
| R2-2207285 |
RAN2 Aspects of Network-Controlled Repeater |
Qualcomm Inc. |
| R2-2207291 |
Overview of network-controlled repeaters |
NEC Telecom MODUS Ltd. |
| R2-2207413 |
Discussion on functionality for NCR-MT |
Fujitsu |
| R2-2207459 |
Discussion on identification and authorization of NCR |
Apple |
| R2-2207485 |
General consideration on NCR management |
Huawei, HiSilicon |
| R2-2207517 |
Identification and Authorization of Network-controlled Repeater |
CATT |
| R2-2207691 |
Network-controlled repeaters - key issues |
Samsung R&D Institute UK |
| R2-2207717 |
Discussion on identification and authorization for network-controlled repeaters |
Lenovo |
| R2-2207825 |
Considerations on NCR authorization and fwd link config |
Sony |
| R2-2208034 |
Identification and authorization of NCRs: capabilities and attributes management |
Philips International B.V. |
| R2-2208110 |
Considertion on NCR identification and authorization |
ZTE Corporation, Sanechips |
| R2-2208198 |
Discussion on RAN2 topics for NCR |
Ericsson |
| R2-2208293 |
Initial consideration on Network-controlled repeaters |
Kyocera |
| R2-2208390 |
Identification and authorization of network-controlled repeaters |
MediaTek Beijing Inc. |
| R2-2208416 |
Multi-frequency support to enable control links for NR network-controlled repeaters |
AT&T |
| R2-2208447 |
Discussion on the network-controlled repeater management |
CMCC |
| R2-2208458 |
Discussion on NCR Related Procedures |
vivo |
| R2-2208628 |
Discussion on identification and authorization of Network-controlled Repeaters |
China Telecom |
| R2-2208658 |
Initial discussion on Network Control Repeater |
Rakuten Mobile, Inc |
| R2-2208886 |
[Pre119-e][701][NCR] Summary of AI 8.1 network-controlled repeaters |
ZTE Corporation |
| R2-2208887 |
TP to TR 38.867 about RAN2 (Uu related) part |
ZTE Corporation |
| R2-2208888 |
TP to TR 38.867 about RAN2 (Uu related) part |
ZTE Corporation |
| R2-2208889 |
[DRAFT] LS on the progress of NCR identification and authorization |
ZTE Corporation |
| R2-2208890 |
LS on the progress of NCR identification and authorization |
RAN2 |
| 8.2.1 |
Organizational |
|
| R2-2207105 |
Summary of pre-discussion on Rel-18 expanded and improved NR positioning |
CATT |
| R2-2207387 |
RAN1 agreements on Expanded and improved NR positioning |
Intel Corporation |
| R2-2207737 |
Work Plan for Study Item on Expanded and Improved NR Positioning |
CATT, Intel Corporation, Ericsson |
| 8.2.2 |
Sidelink positioning |
|
| R2-2207081 |
Discussion on sidelink positioning |
vivo |
| R2-2207090 |
Discussion of sidelink positioning |
OPPO |
| R2-2207106 |
SL Positioning Architecture and Protocol Stack |
CATT |
| R2-2207229 |
Discussion of sidelink positioning procedures |
Nokia Germany |
| R2-2207286 |
Principles for sidelink positioning |
MediaTek Inc. |
| R2-2207388 |
Support of sidelink positioning |
Intel Corporation |
| R2-2207435 |
On Sidelink Positioning Architecture |
Apple |
| R2-2207486 |
Discussion on Sidelink Positioning |
InterDigital, Inc. |
| R2-2207586 |
Discussion on sidelink positioning |
ZTE, Sanechips |
| R2-2207684 |
Discussion on potential solutions for SL positioning |
Spreadtrum Communications |
| R2-2207828 |
Considerations on sidelink positioning |
Sony |
| R2-2207865 |
On SL Positioning Architecture and Procedures |
Lenovo |
| R2-2207868 |
Discussion on sidelink positioning |
Huawei, HiSilicon |
| R2-2208080 |
SL positioning |
Ericsson |
| R2-2208126 |
Study of Sidelink Positioning Architecture, Signaling and Procedures |
Qualcomm Incorporated |
| R2-2208253 |
Protocol considerations for sidelink positioning |
Philips International B.V. |
| R2-2208301 |
Discussion on functions of LMF in SL positioning |
Samsung |
| R2-2208320 |
Discussion on out-of-coverage sidelink positioning |
Samsung R&D Institute UK |
| R2-2208453 |
Initial considerations on Sidelink positioning |
CMCC |
| R2-2208582 |
Discussion on SL positioning |
Xiaomi |
| R2-2208685 |
Discussion of sidelink positioning procedures |
Nokia, Nokia Shanghai Bell |
| 8.2.3 |
RAT-dependent integrity |
|
| R2-2207082 |
Discussion on RAT-dependent integrity |
vivo |
| R2-2207107 |
Discussion on RAT dependent integrity |
CATT |
| R2-2207389 |
Support of RAT dependent integrity |
Intel Corporation |
| R2-2207487 |
Discussion on RAT-dependent Integrity |
InterDigital, Inc. |
| R2-2207585 |
Discussion on RAT-dependent methods positioning integrity |
ZTE, Sanechips |
| R2-2207685 |
Discussion on solutions for integrity of RAT-dependent positioning techniques |
Spreadtrum Communications |
| R2-2207702 |
Discussion on RAT-dependent positioning integrity |
Lenovo |
| R2-2207829 |
Considerations on solution for integrity of RAT dependent positioning |
Sony |
| R2-2207869 |
Discussion on RAT-dependent integrity |
Huawei, HiSilicon |
| R2-2207911 |
Discussion on RAT-dependent positioning integrity |
Xiaomi |
| R2-2208079 |
RAT-dependent integrity |
Ericsson |
| R2-2208127 |
Integrity of NR Positioning Technologies |
Qualcomm Incorporated |
| R2-2208318 |
Discussion on integrity of RAT dependent positioning techniques |
Samsung R&D Institute UK |
| R2-2208322 |
Discussion of RAT-dependent positioning integrity |
Nokia, Nokia Shanghai Bell |
| 8.2.4 |
LPHAP |
|
| R2-2207083 |
Discussion on LPHAP |
vivo |
| R2-2207089 |
Consideration on LPHAP |
OPPO |
| R2-2207111 |
Discussion on LPHAP |
CATT |
| R2-2207390 |
Support of LPHAP |
Intel Corporation |
| R2-2207436 |
On LPHAP |
Apple |
| R2-2207488 |
Discussion on LPHAP |
InterDigital, Inc. |
| R2-2207584 |
Discussion on LPHAP |
ZTE, Sanechips |
| R2-2207703 |
Discussion on low power high accuracy positioning |
Lenovo |
| R2-2207830 |
Considerations on solution for Low Power High Accuracy Positioning |
Sony |
| R2-2207867 |
Discussion on the LPHAP |
Huawei, HiSilicon |
| R2-2207912 |
Discussion on LPHA positioning |
Xiaomi |
| R2-2208078 |
Discussion on Low Power High Accuracy Positioning |
Ericsson |
| R2-2208128 |
Limitations of RRC_INACTIVE positioning for LPHAP |
Qualcomm Incorporated |
| R2-2208180 |
Use case and area of focus for LPHAP study |
Nokia, Nokia Shanghai Bell |
| R2-2208454 |
Initial considerations on LPHAP |
CMCC |
| R2-2208626 |
Discussion on the LPHAP |
Huawei, HiSilicon, Deutsche Telekom |
| 8.3.1 |
Organizational |
|
| R2-2208339 |
Work plan for NR network energy savings |
Huawei |
| R2-2208340 |
TR 38.864 skeleton for study on network energy savings for NR |
Huawei |
| R2-2208341 |
General consideration of RAN2 study |
Huawei |
| R2-2209016 |
LS on skeleton of TR 38.864 for NR network energy savings (R3-225203; contact: Huawei) |
RAN3 |
| 8.3.2 |
gNB and UE supporting techniques |
|
| R2-2207037 |
Discussion on NW energy saving |
KDDI Corporation |
| R2-2207115 |
Efficient operation of adaptation for network energy saving |
Intel Corporation |
| R2-2207116 |
Additional UE assistance information and UE feedback |
Intel Corporation |
| R2-2207246 |
Time domain NES techniques |
InterDigital |
| R2-2207247 |
Frequency domain and UE assistance NES techniques |
InterDigital |
| R2-2207292 |
Finer granularity configuration for NES |
NEC Telecom MODUS Ltd. |
| R2-2207293 |
Assistance information to support choice of NES configuration |
NEC Telecom MODUS Ltd. |
| R2-2207406 |
Consideration on network energy saving |
Fujitsu |
| R2-2207414 |
Efficient PCell and SCell handling for network energy saving |
Fujitsu |
| R2-2207423 |
Initial discussion on RAN2 work of Network energy saving |
Apple |
| R2-2207424 |
On-demand measurement for network energy saving |
Apple |
| R2-2207511 |
Network energy savings: issues for investigation in RAN2 |
CATT |
| R2-2207512 |
Consideration on UE Assistance Information |
CATT |
| R2-2207545 |
NW energy saving in CONNECTED |
Nokia, Nokia Shanghai Bell |
| R2-2207546 |
NW energy saving in IDLE |
Nokia, Nokia Shanghai Bell |
| R2-2207786 |
discussions on time domain techniques for network energy saving |
vivo |
| R2-2207787 |
discussion on frequency domain and UE-assisted Network Energy saving techniques |
vivo |
| R2-2207799 |
Discussion on network energy savings |
OPPO |
| R2-2207800 |
Discussion on the UE assistance information |
OPPO |
| R2-2207919 |
Discussion on supporting of network energy savings for NR |
Lenovo |
| R2-2207920 |
Discussion on the state transition in NES |
Lenovo |
| R2-2207960 |
Alignment of UE and Network Energy Saving |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2208026 |
Assistance information from the UE for NW energy savings |
Ericsson |
| R2-2208031 |
Miscellaneous mechanisms for network energy savings |
Ericsson |
| R2-2208120 |
Network Energy Savings Techniques |
Qualcomm Incorporated |
| R2-2208233 |
gNB operation for NES |
ETRI |
| R2-2208297 |
Network Energy savings - UE grouping for efficient signaling |
Rakuten Mobile, Inc |
| R2-2208330 |
Supporting access via assistant cell for network energy saving |
ZTE corporation, Sanechips |
| R2-2208331 |
Techniques in various domains and UE assistance information for network energy saving |
ZTE corporation, Sanechips |
| R2-2208342 |
Discussion on network energy saving techniques for single carrier |
Huawei, HiSilicon, Deutsche Telekom |
| R2-2208343 |
Discussion on network energy saving techniques for multi-carrier case |
Huawei, HiSilicon, China Unicom, Deutsche Telekom |
| R2-2208431 |
Discussion on the technical directions for network energy saving |
CMCC |
| R2-2208432 |
Analysis on power consumption in base station |
CMCC |
| R2-2208573 |
Energy saving on system information transmission |
Xiaomi |
| R2-2208592 |
Feedback and Assistance Information for NES |
Samsung |
| R2-2208593 |
Network Energy Saving (NES) Techniques |
Samsung |
| R2-2208606 |
Coexistence considerations in network energy saving |
MediaTek Inc. |
| 8.4.1 |
Organizational |
|
| R2-2206981 |
RAN2 Work Plan for Rel-18 Further NR Mobility Enhancements WI |
MediaTek Inc., Apple |
| 8.4.2.1 |
Target Performance Enhancements |
|
| R2-2206982 |
Target Performance Enhancements for L1L2-based Inter-cell Mobility |
MediaTek Inc. |
| R2-2206992 |
On the Target Performance Enhancements for L1L2 based Mobility |
CATT |
| R2-2207315 |
NR mobility issues and goals for improvement |
Futurewei |
| R2-2207340 |
L1/L2 Mobility – General Concepts and Configuration |
Qualcomm Incorporated |
| R2-2207380 |
Discussion on latency model of L1 L2 mobility |
Intel Corporation |
| R2-2207407 |
Consideration on L1/L2 signalling based mobility |
Fujitsu |
| R2-2207466 |
Latency reduction aspects of L2/L1 mobility |
Apple |
| R2-2207496 |
Target scenario and latency reduction in L1/L2 based mobility |
NEC |
| R2-2207537 |
Discussion on Dynamic switch mechanism among candidate serving cells |
KDDI Corporation |
| R2-2207637 |
L1/L2 mobility target performance enhancements |
Huawei, HiSilicon |
| R2-2207655 |
Analysis of HO latency and possible enhancements for L1/L2 mobility |
OPPO |
| R2-2207752 |
Discussion on basic model for L1 L2 mobility |
vivo |
| R2-2207806 |
Latency Evaluation of L1 or L2 based mobility |
Xiaomi |
| R2-2207857 |
Initial discussion of L1/L2 mobility |
Sharp |
| R2-2207918 |
Applicable scenarios for L1/L2 based mobility enhancements |
Vodafone |
| R2-2208185 |
Target enhancements and latency model for L1/2 triggered handover |
Interdigital, Inc. |
| R2-2208200 |
Latency analysis for L1/L2 based inter-cell mobility |
Ericsson |
| R2-2208212 |
Prerequisites and benefits of Lower Layer Mobility |
Nokia, Nokia Shanghai Bell |
| R2-2208367 |
Discussion on L1 L2 mobility performance enhancement |
ASUSTeK |
| R2-2208455 |
Initial considerations on L1L2 mobility |
CMCC |
| R2-2208522 |
L1/L2 mobility scenarios and latency |
LG Electronics |
| R2-2208528 |
Scenario and Target Performance Enhancements for L1/L2 mobility |
Samsung |
| R2-2208559 |
Initial Consideration on L1-L2 Signaling Based Mobility |
ZTE Corporation,Sanechips |
| R2-2209255 |
38.300 running CR for introduction of NR further mobility enhancements |
MediaTek Inc. |
| R2-2209256 |
Report of [Post119-e][036][feMob] Time Chart |
MediaTek Inc. |
| R2-2209257 |
LS on L1/L2-based inter-cell mobility |
RAN2 |
| 8.4.2.2 |
Candidate Solutions |
|
| R2-2206983 |
Candidate Solutions for L1L2-based Inter-cell Mobility |
MediaTek Inc. |
| R2-2206993 |
Discussion on Solutions for L1L2 Based Inter-Cell Mobility |
CATT |
| R2-2207316 |
Suggested solutions for L1/L2 mobility enhancement |
Futurewei |
| R2-2207339 |
L1 L2 inter-cell mobility design principles |
Lenovo |
| R2-2207381 |
Discussion on candidate solutions of L1 L2 mobility |
Intel Corporation |
| R2-2207467 |
Basic Agreements for Candidate Solutions |
Apple |
| R2-2207497 |
Possible solutions for L1/L2 based mobility |
NEC |
| R2-2207535 |
Discussion on L1L2 mobility |
NTT DOCOMO INC. |
| R2-2207656 |
Discussion on measurement and reporting of L1/L2 mobility |
OPPO |
| R2-2207657 |
Initial considerations on L1/L2 mobility |
OPPO |
| R2-2207681 |
Discussion on L1/L2 based inter-cell mobility |
Spreadtrum Communications |
| R2-2207738 |
Solutions for L1 L2 mobility |
Huawei, HiSilicon |
| R2-2207753 |
Discussion on candidate solutions for L1 L2 mobility |
vivo |
| R2-2207807 |
Candidate solutions for L1 L2 based inter-cell mobility |
Xiaomi |
| R2-2208186 |
Support for L1/2 triggered handover |
Interdigital, Inc. |
| R2-2208199 |
Configuration of candidate target cells for L1/L2 based inter-cell mobility |
Ericsson |
| R2-2208201 |
Solutions for L1/L2 based inter-cell mobility |
Ericsson |
| R2-2208213 |
Basic details of Lower Layer L1/L2 Mobility |
Nokia, Nokia Shanghai Bell |
| R2-2208325 |
Discussion on L1L2 mobility |
LG Electronics Inc. |
| R2-2208326 |
General aspects of L1L2 based inter-cell mobility |
LG Electronics Inc. |
| R2-2208368 |
Discussion on L1 L2 mobility procedure |
ASUSTeK |
| R2-2208409 |
Candidate solutions for L1/L2 mobility |
ZTE Corporation, Sanechips |
| R2-2208456 |
Potential solutions for L1L2 mobility |
CMCC |
| R2-2208529 |
Considerations on the L1/L2 Inter-Cell Mobility |
Samsung |
| R2-2208699 |
Suggested solutions for L1/L2 mobility enhancement |
Futurewei |
| 8.4.3 |
NR-DC with selective activation cell of groups |
|
| R2-2206994 |
Discussion on Selective Activation of Cell Groups in NR-DC |
CATT |
| R2-2207125 |
Discussion on requirement for subsequent CG change |
PANASONIC R&D Center Germany |
| R2-2207317 |
Pre-configuring and handling multiple candidates for NR-DC |
Futurewei |
| R2-2207382 |
Discussion on NR-DC with selective activation cell of groups |
Intel Corporation |
| R2-2207468 |
Setting the stage for practical operation of selective activation of cell groups |
Apple |
| R2-2207498 |
Overview of selective CG activation |
NEC |
| R2-2207534 |
Discussion on selective activation |
NTT DOCOMO INC. |
| R2-2207638 |
NR-DC with selective activation of SCG |
Huawei, HiSilicon |
| R2-2207658 |
Discussion on selective activation of cell groups |
OPPO |
| R2-2207677 |
Discussion on NR-DC with selective activation cell of groups |
Spreadtrum Communications |
| R2-2207694 |
On selective cell group activation |
Lenovo |
| R2-2207726 |
NR-DC with selective activation |
Ericsson |
| R2-2207754 |
Discussion on NR-DC with selective activation cell of groups |
vivo |
| R2-2207858 |
Initial discussion of selective activation |
Sharp |
| R2-2207910 |
Aspects to improve for the support of subsequent CPC |
NEC |
| R2-2207917 |
Further mobility enhancements for NR-DC |
Vodafone Telekomünikasyon A.S. |
| R2-2207922 |
Selective Cell Group Activation |
LG Electronics Finland |
| R2-2208036 |
Analysis of applicable scenarios and problems for NR-DC selective activation procedure |
Nokia, Nokia Shanghai Bell |
| R2-2208145 |
Configuration and activation of multiple cell groups in NR-DC |
Qualcomm Incorporated |
| R2-2208264 |
Selective activation of cell groups |
InterDigital, Inc. |
| R2-2208410 |
Discussion on NR-DC with selective activation of the cell groups |
ZTE Corporation, Sanechips |
| R2-2208451 |
Discussion on NR-DC with selective activation cell of groups |
CMCC |
| R2-2208467 |
Discussion on NR-DC with selective activation of the cell groups |
Xiaomi |
| R2-2208477 |
Discussion on selective activation of CG |
MediaTek Inc. |
| R2-2208530 |
Considerations on subsequent CPAC after SCG change |
Samsung |
| 8.4.4 |
Other |
|
| R2-2206995 |
Discussion on CHO including target MCG and candidate SCGs for CPC/CPA |
CATT |
| R2-2207325 |
First thoughts on Conditional Handover with candidate SCGs for CPAC |
Nokia, Nokia Shanghai Bell |
| R2-2207383 |
Discussion on CHO including candidate SCGs |
Intel Corporation |
| R2-2207695 |
Failure case for CHO with SCG |
Lenovo |
| R2-2207696 |
CHO with target MCG and candidate SCG |
Lenovo |
| R2-2207739 |
CHO including candidate SCGs for CPC/CPA |
Huawei, HiSilicon |
| R2-2207755 |
Discussion on CHO with CPAC |
vivo |
| R2-2207848 |
Considerations on CHO+CPA/CPC |
Samsung |
| R2-2207859 |
Support of SCG deactivation with conditional reconfiguration |
Sharp |
| R2-2208144 |
CHO including target MCG and candidate SCGs |
Qualcomm Incorporated |
| R2-2208262 |
CHO with associated SCG |
InterDigital, Inc. |
| R2-2208411 |
Discussion on CHO with candidate SCG |
ZTE Corporation, Sanechips |
| R2-2208468 |
CHO with one or multiple candidate SCGs |
Xiaomi |
| R2-2208475 |
Discussion and clarification on CHO enhancement scenarios |
MediaTek Inc. |
| 8.5.1 |
Organizational |
|
| R2-2206917 |
LS on draft TR 38.835 skeleton (R1-2205443; contact: Nokia) |
RAN1 |
| R2-2206923 |
Reply LS on UE Power Saving for XR and Media Services (R1-2205531; contact: Qualcomm) |
RAN1 |
| R2-2206964 |
LS on QoS support with PDU Set granularity (S2-2201803; contact: Intel) |
SA2 |
| R2-2206966 |
LS on UE Power Saving for XR and Media Services (S2-2203418; contact: Nokia) |
SA2 |
| R2-2206969 |
LS Reply on QoS support with PDU Set granularity (S4-220505; contact: Qualcomm) |
SA4 |
| R2-2207042 |
Draft reply LS on UE power savings for XR and media services |
Qualcomm Incorporated |
| R2-2207371 |
Work Plan for Rel-18 SI on XR Enhancements for NR |
Nokia, Qualcomm (Rapporteurs) |
| R2-2207372 |
XR TR Structure |
Nokia (Rapporteur) |
| R2-2207373 |
TR 83.835 v001 |
Nokia (Rapporteur) |
| R2-2207374 |
TR 83.835 v002 |
Nokia (Rapporteur) |
| R2-2207375 |
XR Overview TP |
Nokia (Rapporteur) |
| R2-2207376 |
Draft LS to SA4 on Pose Information for XR |
Nokia (Rapporteur) |
| R2-2208316 |
Discussion of SA2 LS on UE Power Saving for XR and Media Services |
Meta Ireland |
| R2-2208748 |
TR 83.835 v002 |
Nokia (Rapporteur) |
| R2-2208749 |
TR 83.835 v002 |
Nokia (Rapporteur) |
| R2-2209213 |
LS on Pose Information for XR |
RAN2 |
| R2-2209215 |
LS on XR-awareness in RAN |
RAN2 |
| R2-2209220 |
TR 83.835 v002 |
Nokia (Rapporteur) |
| 8.5.2 |
XR-awareness |
|
| R2-2207044 |
XR-awareness in RAN |
Qualcomm Incorporated |
| R2-2207117 |
XR awareness: RAN2 areas of interest, assumptions, and inputs to SA2 LS |
Intel Corporation |
| R2-2207118 |
Solution Directions for XR Specific Differentiated Traffic Handling and Packet Dropping |
Intel Corporation |
| R2-2207197 |
Discussion on XR-awareness |
NTT DOCOMO, INC. |
| R2-2207210 |
Discussing on XR-awareness in RAN |
Xiaomi Communications |
| R2-2207366 |
Discussion on XR-awareness |
TCL Communication |
| R2-2207377 |
XR Awareness in SA2 |
Nokia (Rapporteur) |
| R2-2207429 |
Considerations on XR-awareness, QoS-metrics, and XR-specific traffic handling |
Apple |
| R2-2207489 |
Discussion on XR-awareness |
InterDigital, Inc. |
| R2-2207508 |
XR requirements and issues |
CATT |
| R2-2207680 |
Discussion on RAN awareness of XR traffic characteristics |
Spreadtrum Communications |
| R2-2207697 |
Discusion of XR awareness in RAN |
Lenovo |
| R2-2207756 |
Discussion on XR-awareness |
vivo |
| R2-2207761 |
Discussion on XR-awareness |
III |
| R2-2207780 |
Discussion on XR-awareness |
KT Corp. |
| R2-2207801 |
Discussion on XR-awareness in RAN |
OPPO |
| R2-2207831 |
Considerations on XR awareness |
Sony |
| R2-2207893 |
XR-awareness techniques |
Google Inc. |
| R2-2207926 |
First steps for XR handling |
Vodafone GmbH |
| R2-2207980 |
RAN level protocol enhancements for XR awareness |
ZTE Corporation, Sanechips |
| R2-2207991 |
Views on XR-specific handling at RAN |
Huawei, HiSilicon |
| R2-2207998 |
On RAN awareness of XR traffic characteristics |
MediaTek Inc. |
| R2-2208021 |
Draft LS on first steps for XR handling |
Vodafone GmbH |
| R2-2208223 |
RAN behaviour for XR-awareness QoS |
ETRI |
| R2-2208259 |
Discussion on XR awareness |
Samsung |
| R2-2208313 |
Discussion on XR-Awareness RAN |
Meta Ireland |
| R2-2208321 |
Discussion on XR-awareness |
LG Electronics Inc. |
| R2-2208443 |
Consideration on XR-awareness in RAN |
CMCC |
| R2-2208618 |
Discussion on XR traffic characteristics |
Futurewei |
| R2-2208677 |
Discussion on XR-awareness |
Ericsson |
| 8.5.3 |
XR-specific power saving |
|
| R2-2206986 |
Discussion on XR-specific power saving |
FGI |
| R2-2206996 |
Discussion on CDRX enhancement for XR |
OPPO |
| R2-2207045 |
Power saving enhancements for XR |
Qualcomm Incorporated |
| R2-2207084 |
Consideration on CDRX enhancement for XR |
KDDI Corporation |
| R2-2207119 |
Study of C-DRX enhancements for XR traffic |
Intel Corporation |
| R2-2207171 |
Discussion on XR power saving |
III |
| R2-2207211 |
Discussing on XR-specific power saving |
Xiaomi Communications |
| R2-2207294 |
C-DRX enhancement for XR-specific power saving |
NEC Telecom MODUS Ltd. |
| R2-2207368 |
Discussion on XR-specific power saving |
TCL Communication |
| R2-2207409 |
Discussion on XR-specific power saving techniques |
DENSO CORPORATION |
| R2-2207430 |
Power Saving for Periodical XR Traffics |
Apple |
| R2-2207490 |
Discussion on XR-specific power saving |
InterDigital, Inc. |
| R2-2207509 |
Consideration on power saving for XR services |
CATT |
| R2-2207569 |
DRX enhancement for power saving in XR |
LG Electronics Inc. |
| R2-2207673 |
Discussion on power saving in XR |
Spreadtrum Communications |
| R2-2207757 |
Discussion on XR-specific power saving |
vivo |
| R2-2207832 |
Considerations on XR specific C-DRX power saving enhancements |
Sony |
| R2-2207846 |
Discussion on power saving scheme for XR |
Samsung |
| R2-2207864 |
XR-specific power saving techniques |
Google Inc. |
| R2-2207877 |
Discussion on Power saving enhancements |
Lenovo |
| R2-2207888 |
Discussion on XR-specific power saving techniques |
Huawei, HiSilicon |
| R2-2207979 |
Power Saving enhancements for XR |
ZTE Corporation, Sanechips |
| R2-2207999 |
C-DRX enhancements for XR |
MediaTek Inc. |
| R2-2208019 |
XR power saving RAN1 study overview and suggestions for RAN2 focus |
Nokia, Nokia Shanghai Bell (Rapporteur) |
| R2-2208020 |
XR Power Saving enhancements |
Nokia, Nokia Shanghai Bell |
| R2-2208295 |
Draft Reply LS on UE Power Saving for XR and Media Services |
Nokia |
| R2-2208440 |
Discussion on XR-specific power saving |
CMCC |
| R2-2208620 |
Impacts of XR traffics on UE power saving |
Futurewei |
| R2-2208680 |
Discussion on power saving enhancements for XR |
Ericsson |
| 8.5.4 |
XR-specific capacity improvements |
|
| R2-2207050 |
Capacity enhancements for XR |
Qualcomm Israel Ltd. |
| R2-2207173 |
Discussion on the UL enhancement for XR |
ITRI |
| R2-2207212 |
Discussing on XR-specific capacity improvements |
Xiaomi Communications |
| R2-2207295 |
XR-specific capacity improvements |
NEC Telecom MODUS Ltd. |
| R2-2207367 |
Discussion on XR-specific capacity improvements |
TCL Communication |
| R2-2207378 |
XR Capacity Improvements |
Nokia, Nokia Shanghai Bell |
| R2-2207410 |
Discussion on XR-specific capacity improvements |
DENSO CORPORATION |
| R2-2207431 |
Capacity Enhancement based on XR PDU Set Characteristics |
Apple |
| R2-2207491 |
Discussion on XR-specific capacity improvements |
InterDigital, Inc. |
| R2-2207510 |
XR-specific Capacity Improvement |
CATT |
| R2-2207674 |
Some improvements on XR capacity |
Spreadtrum Communications |
| R2-2207719 |
XR-specific capacity improvements |
MediaTek Beijing Inc. |
| R2-2207758 |
Discussion on XR Capacity Enhancements |
vivo |
| R2-2207762 |
Discussion on XR-specific capacity improvements |
III |
| R2-2207785 |
Discussion on XR capacity improvements |
KT Corp. |
| R2-2207802 |
Discussion on XR-specific capacity improvements |
OPPO |
| R2-2207833 |
Considerations on XR specific capacity improvements |
Sony |
| R2-2207878 |
Discussion on XR-specific capacity enhancements |
Lenovo |
| R2-2207921 |
XR-specific capacity improvements |
Google Inc. |
| R2-2207978 |
Capacity enhancements of XR support in RAN |
ZTE Corporation, Sanechips |
| R2-2208232 |
Scheduling method for XR packets |
ETRI |
| R2-2208302 |
Discussion on XR-specific capacity improvement |
Samsung |
| R2-2208401 |
Discussion on Capacity enahancement for XR |
LG Electronics Inc. |
| R2-2208417 |
Support for XR-specific scheduler enhancements |
AT&T |
| R2-2208422 |
Discussion on XR-specific capacity improvements |
CMCC |
| R2-2208498 |
Discussion on XR-specific capacity enhancements techniques |
Huawei, HiSilicon |
| R2-2208621 |
Layer 2 based XR capacity enhancement |
Futurewei |
| R2-2208676 |
XR capacity enhancements |
Ericsson |
| 8.6.2 |
Performance Enhancements |
|
| R2-2207060 |
Discussion on HARQ enhancement for IoT NTN |
OPPO |
| R2-2207075 |
Discussion on GNSS operation in connected mode |
OPPO |
| R2-2207300 |
On Disabling HARQ Feedback in IoT-NTN |
MediaTek Inc. |
| R2-2207354 |
HARQ process enhancements |
Qualcomm Incorporated |
| R2-2207484 |
Discussion on HARQ feedback disabling |
Huawei, HiSilicon |
| R2-2207647 |
Discussion on performance enhancement for IoT NTN |
Transsion Holdings |
| R2-2207710 |
Considerations on reducing UE GNSS operations in long connection time |
Lenovo |
| R2-2207841 |
Consideration on HARQ and GNSS enhancements |
ZTE Corporation, Sanechips |
| R2-2208187 |
Disabling HARQ feedback for IoT-NTN |
Interdigital, Inc. |
| R2-2208388 |
Discussion on the HARQ disabling in IoT NTN |
CATT |
| R2-2208448 |
Discussion on the performance enhancement for IoT-NTN |
CMCC |
| R2-2208565 |
Discussion on HARQ feedback disabling for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208585 |
Discussion on disabling of HARQ feedback |
Xiaomi |
| R2-2209043 |
Report of [AT119-e][ IoT-NTN] LS to RAN1 (Mediatek) |
MediaTek |
| 8.6.3 |
Mobility Enhancements |
|
| R2-2207061 |
Discussion on mobility enhancement for IoT NTN |
OPPO |
| R2-2207275 |
Discussion on neighbour cell measurements in IoT NTN |
Intel Corporation |
| R2-2207299 |
On Mobility Enhancements in IoT-NTN |
MediaTek Inc. |
| R2-2207355 |
Connected mode mobility enhancements |
Qualcomm Incorporated |
| R2-2207500 |
Discussion on mobility enhancements for IoT NTN |
Huawei, HiSilicon |
| R2-2207648 |
Discussion on mobility enhancement for IoT NTN |
Transsion Holdings |
| R2-2207682 |
Discussion on triggering neighbour cell measurement before RLF |
Spreadtrum Communications |
| R2-2207711 |
Considerations on neighbour cell measurement for NB-IoT in NTN scenario |
Lenovo |
| R2-2207842 |
Consideration on mobility enhancements |
ZTE Corporation, Sanechips |
| R2-2207913 |
Discussion on mobility enhancements to IoT NTN |
Xiaomi |
| R2-2207931 |
Mobility Enhancement for IoT NTN |
Samsung R&D Institute UK |
| R2-2207939 |
Neighbour cell measurements before RLF |
Apple |
| R2-2208037 |
Changes to current mobility enhancement procedures for IoT-NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208146 |
Discussion on Mobility Enhancements |
TURKCELL |
| R2-2208188 |
IoT-NTN mobility enhancements |
Interdigital, Inc. |
| R2-2208389 |
Discussion on the mobility enhancements in eMTC |
CATT |
| R2-2208449 |
Discussion on the mobility enhancement for IoT-NTN |
CMCC |
| R2-2208518 |
Use of Elevation Angle Threshold for IoT NTN Neighbour Cell Measurements |
SHARP Corporation |
| R2-2208673 |
R18 IoT NTN Mobility enhancements |
Ericsson |
| 8.6.4 |
Enhancements to discontinuous coverage |
|
| R2-2207301 |
Enhancements to discontinuous coverage in IoT-NTN |
MediaTek Inc. |
| R2-2207356 |
RRC release procedure in discontinuous coverage |
Qualcomm Incorporated |
| R2-2207483 |
Discussion on the discontinuous coverage |
Huawei, HiSilicon |
| R2-2207649 |
Discussion on enhancement to discontinuous coverage for IoT NTN |
Transsion Holdings |
| R2-2207683 |
Discussion on power saving mechanism for supporting discontinuous coverage |
Spreadtrum Communications |
| R2-2207712 |
Considerations on mobility management and power saving for discontinuous coverage |
Lenovo |
| R2-2207778 |
Power Saving Enhancement for Discontinuous Coverage |
Google Inc. |
| R2-2207843 |
Consideration on discontinuous coverage enhancements |
ZTE Corporation, Sanechips |
| R2-2207914 |
Discussion on enhancements to discontinuous coverage |
Xiaomi |
| R2-2208023 |
Enhancements to discontinuous coverage |
Samsung R&D Institute UK |
| R2-2208115 |
Power Saving Enhancement for Discontinuous Coverage |
Samsung R&D Institute UK |
| R2-2208189 |
IoT-NTN discontinuous coverage enhancements |
Interdigital, Inc. |
| R2-2208450 |
Discussion on the discontinuous coverage for IoT-NTN |
CMCC |
| R2-2208566 |
Discussion on Discontinuous Coverage for IoT NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208663 |
Discussion on Enhancements related to discontinuous coverage |
Rakuten Mobile, Inc |
| R2-2208672 |
R18 IoT NTN Enhancements to discontinuous coverage |
Ericsson |
| 8.7.1 |
Organizational |
|
| R2-2207096 |
R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 |
THALES |
| R2-2208779 |
LS on LCS framework for Network verified UE location (NTN) |
RAN2 |
| 8.7.2 |
Coverage Enhancements |
|
| R2-2207346 |
Protocol overhead reduction for coverage enhancements |
Qualcomm Incorporated |
| R2-2207633 |
Discussion on RAN overhead reduction for VoNR support in NR NTN |
vivo |
| R2-2207713 |
Potential issues for Msg3 repetition in NTN |
Lenovo |
| R2-2208276 |
Blind Msg3 retransmission in Rel-18 NTN |
InterDigital |
| R2-2208323 |
Discussion on the coverage enhancement in NTN |
LG Electronics Inc. |
| R2-2208375 |
Analysis on NTN Coverage Enhancement |
CATT |
| R2-2208567 |
On Coverage Enhancements for NR NTN |
Nokia, Nokia Shanghai Bell |
| R2-2208586 |
Discussion on coverage enhancement for NR NTN |
Xiaomi |
| R2-2208612 |
Discussion on RAN protocol overhead reduction |
Huawei, HiSilicon |
| 8.7.3 |
Network verified UE location |
|
| R2-2207074 |
Discussion on network verified UE location |
OPPO |
| R2-2207098 |
Network verified UE location aspects |
THALES |
| R2-2207274 |
Discussion on network verified UE location |
Intel Corporation |
| R2-2207296 |
Assumptions on Network verified location |
NEC Telecom MODUS Ltd. |
| R2-2207302 |
On Network Verified UE Location in NR-NTN |
MediaTek Inc. |
| R2-2207326 |
Considerations on NW-verified UE location |
Nokia, Nokia Shanghai Bell |
| R2-2207444 |
Consideration on NTN Network Verified UE Location |
Apple |
| R2-2207482 |
Discussion on the network verfied UE location |
Huawei, HiSilicon |
| R2-2207634 |
Discussion on NW verification of UE location in Rel-18 NR NTN |
vivo |
| R2-2207645 |
Discussion of Network verified UE location in NTN |
China Telecom |
| R2-2207675 |
Discussion on UE location verify procedure |
Spreadtrum Communications |
| R2-2207779 |
Network Verified UE Location |
Samsung R&D Institute UK |
| R2-2207866 |
On NTN NW verified UE location aspects |
Lenovo |
| R2-2207915 |
Discussion on network verified UE location |
Xiaomi |
| R2-2208022 |
UE location verification in NTN |
Deutsche Telekom, Huawei, HiSilicon |
| R2-2208328 |
Discussion on Network Verified UE Location |
NTT DOCOMO INC. |
| R2-2208376 |
Discussion on UE Location Verification |
CATT |
| R2-2208444 |
Consideration on UE Location Verification via Network |
CMCC |
| R2-2208546 |
Consideration on NW verified UE location |
ZTE Corporation, Sanechips |
| R2-2208674 |
R18 NR NTN Network verified UE location |
Ericsson |
| R2-2208775 |
Network verified UE location aspects |
THALES |
| 8.7.4 |
NTN-TN and NTN-NTN mobility and service continuity enhancements |
|
| R2-2207022 |
Discussion on assistance information of cell reselection for NTN-TN mobility |
ITRI |
| R2-2207048 |
Discussion on mobility enhancements in Rel-18 NTN |
New H3C Technologies Co., Ltd. |
| R2-2207062 |
Discussion on mobility enhancements for idle and inactive UEs |
OPPO |
| R2-2207073 |
Discussion on NTN handover enhancements |
OPPO |
| R2-2207195 |
Discussion on NTN-TN and NTN-NTN mobility |
NTT DOCOMO, INC. |
| R2-2207244 |
NTN mobility enhancements in connected mode |
Samsung Research America |
| R2-2207245 |
NTN cell reselection enhancements |
Samsung Research America |
| R2-2207272 |
Discussion on NTN handover enhancements |
Intel Corporation |
| R2-2207273 |
Discussion on NTN cell reselection enhancements |
Intel Corporation |
| R2-2207297 |
NTN-NTN handover enhancement for RRC_CONNECTED UEs |
NEC Telecom MODUS Ltd. |
| R2-2207298 |
Solutions to reduce UE power consumption for NTN to TN mobility in Idle or Inactive mode |
NEC Telecom MODUS Ltd. |
| R2-2207303 |
Improving Cell Reselection in NR-NTN |
MediaTek Inc. |
| R2-2207304 |
Handover Enhancement in LEO NTN with Earth-moving Cells |
MediaTek Inc. |
| R2-2207327 |
On NTN-NTN and TN-NTN mobility in Rel-18 |
Nokia, Nokia Shanghai Bell |
| R2-2207347 |
Signaling and congestion reduction in satellite switch |
Qualcomm Incorporated |
| R2-2207348 |
IDLE mode TN-NTN mobility enhancement |
Qualcomm Incorporated |
| R2-2207445 |
NTN-NTN Mobility Enhancement |
Apple |
| R2-2207446 |
NTN-TN Mobility Enhancement |
Apple |
| R2-2207499 |
Discussion on NTN mobility enhancements |
Huawei, HiSilicon |
| R2-2207635 |
Discussion on mobility and service continuity enhancement |
vivo |
| R2-2207646 |
Discussion of NTN-TN mobility |
China Telecom |
| R2-2207650 |
Discussion on NTN mobility and service continuity enhancements |
Transsion Holdings |
| R2-2207676 |
Some enhancements in NTN Handover |
Spreadtrum Communications |
| R2-2207714 |
Issue analysis for service continuity in TN-NTN and NTN-NTN scenarios |
Lenovo |
| R2-2207732 |
Discussion on handover for NTN |
BUPT |
| R2-2207767 |
Discussion on NTN-TN mobility and NTN-NTN mobility |
ITL |
| R2-2207834 |
NTN-TN mobility enhancements |
Sony |
| R2-2207835 |
Signaling overhead reduction during NTN-NTN HOs |
Sony |
| R2-2207892 |
Discussion on handover for NTN |
BUPT |
| R2-2207894 |
Network-driven NTN-NTN Mobility Considerations |
Lockheed Martin |
| R2-2207916 |
Discussion on mobility and service continuity enhancements |
Xiaomi |
| R2-2207986 |
Discussion on target cell's timing for intra-satellite and inter-satellite handover under users of non-uniform spatio -temporal distribution |
BUPT |
| R2-2208147 |
Discussion on ephemeris usage for NR NTN |
TURKCELL |
| R2-2208277 |
RRC Idle/Inactive measurement, mobility, and service continuity |
InterDigital |
| R2-2208278 |
RRC Connected measurement, mobility, and service continuity |
InterDigital |
| R2-2208280 |
Discussion on cell reselection enhancement for NTN |
LG Electronics France |
| R2-2208282 |
Reducing UE power consumption in idle inactive mode |
LG Electronics France |
| R2-2208332 |
Cell reselection enhancements in NTN-NTN and NTN-TN mobility |
ZTE corporation, Sanechips |
| R2-2208333 |
Discussion on NTN-NTN handover enhancement |
ZTE corporation, Sanechips |
| R2-2208377 |
Discussion on NTN Mobility Enhancements |
CATT |
| R2-2208424 |
Discussion on cell reselection enhancements |
CMCC |
| R2-2208425 |
Discussion on mobility enhancements for connected mode |
CMCC |
| R2-2208641 |
Discussion on ephemeris usage for NR NTN |
TURKCELL, Deutsche Telekom |
| R2-2208670 |
R18 NR NTN Mobility enhancements |
Ericsson |
| R2-2208671 |
R18 NR NTN Idle mode Mobility enhancements |
Ericsson |
| 8.8.1 |
Organizational |
|
| R2-2207328 |
Uncrewed Aerial Vehicles in Rel-18 - workplan |
Nokia, Nokia Shanghai Bell |
| 8.8.2 |
Measurement reporting |
|
| R2-2207076 |
Consideration on measurement reporting of NR support for UAV |
DENSO CORPORATION |
| R2-2207154 |
Considerations on Measurement Reports Enhancements |
NEC Europe Ltd |
| R2-2207194 |
Discussion on NR support for UAV |
NTT DOCOMO, INC. |
| R2-2207233 |
Measurement Reports Enhancement for UAV |
OPPO |
| R2-2207329 |
On measurement reporting enhancements for UAVs - LTE baseline in NR framework |
Nokia, Nokia Shanghai Bell |
| R2-2207518 |
Measurement Reporting for NR UAV |
CATT |
| R2-2207601 |
Discussion on measurement reporting enhancement for NR UAV |
vivo |
| R2-2207602 |
Discussion on flight path reporting for NR UAV |
vivo |
| R2-2207624 |
On measurement and reporting enhancements |
Ericsson |
| R2-2207715 |
measurement report enhancement for NR UAV |
Lenovo |
| R2-2207836 |
UAV measurement reporting |
Sony |
| R2-2207925 |
NR support for UAV first steps plus Inter RAT aspects |
Vodafone GmbH |
| R2-2207935 |
Discussion on measurement reporting in UAV |
Apple |
| R2-2208042 |
On measurement and reporting enhancements |
Ericsson |
| R2-2208098 |
Measurement and reporting enhancements |
Qualcomm Incorporated |
| R2-2208099 |
Mobility considerations and some performance results |
Qualcomm Incorporated |
| R2-2208250 |
UAV support for NR |
Intel Corporation |
| R2-2208279 |
Measurement reporting for UAV |
InterDigital |
| R2-2208335 |
Measurement Report Enhancement |
LG Electronics Finland |
| R2-2208336 |
Flight Path Information Enhancement |
LG Electronics Finland |
| R2-2208412 |
Discussion on measurement reporting enhancements for NR UAV |
ZTE Corporation, Sanechips |
| R2-2208421 |
Consideration on subscription-based UAV identification |
Huawei, HiSilicon |
| R2-2208445 |
Consideration on Measurement Reporting for UAV |
CMCC |
| R2-2208469 |
Discussion on measurement reporting for NR UAV |
Xiaomi |
| R2-2208608 |
Discussion on enhancements on measurement reports for NR UAV |
Samsung Electronics Co., Ltd |
| 8.8.3 |
Subscription-based aerial-UE identification |
|
| R2-2207234 |
Subscription-based Aerial-UE Identification |
OPPO |
| R2-2207330 |
On subscription-based UAV UE identification |
Nokia, Nokia Shanghai Bell |
| R2-2207519 |
Subscription-based Aerial-UE Identification for NR |
CATT |
| R2-2208413 |
Discussion on subscription-based identification for NR UAV |
ZTE Corporation, Sanechips |
| R2-2208420 |
Measurement report enhancement for UAV |
Huawei, HiSilicon |
| R2-2208426 |
Discussion on subscription-based aerial-UE identification |
CMCC |
| R2-2208630 |
Discussion on subscription-based aerial-UE identification for NR UAV |
Samsung Electronics Co., Ltd |
| 8.8.4 |
UAV identification broadcast |
|
| R2-2207155 |
Considerations on Enhancements for UAV Identification Broadcast |
NEC Europe Ltd |
| R2-2207626 |
On broadcasting UAV identification |
Ericsson |
| R2-2207716 |
Discussion on broadcasting remote id for UAV |
Lenovo |
| R2-2207837 |
UAV identification broadcast |
Sony |
| R2-2208040 |
On broadcasting UAV identification |
Ericsson |
| R2-2208162 |
UAV Identity broadcast and Identification |
Beijing Xiaomi Mobile Software |
| 8.9.1 |
Organizational |
|
| R2-2208345 |
Work plan for NR sidelink relay enhancements |
LG Electronics France |
| R2-2209194 |
LS on ProSe Authorization information related to UE-to-UE Relay operation to NG-RAN (S2-2207518; contact: LGE) |
SA2 |
| 8.9.2 |
UE-to-UE relay |
|
| R2-2207077 |
Discussion on NR sidelink UE-to-UE relay |
OPPO |
| R2-2207126 |
Discovery and Relay (re-)selection for UE-to-UE relay |
Qualcomm Incorporated |
| R2-2207170 |
Connection management and procedures for L2 UE-to-UE relay |
MediaTek Inc. |
| R2-2207182 |
Discussion on U2U relay discovery and relay selection |
Xiaomi |
| R2-2207198 |
Discussion on U2U relay discovery and (re)selection |
ZTE |
| R2-2207239 |
Discussion on Sidelink U2U Relay Discovery and (Re-)Selection |
Fraunhofer IIS, Fraunhofer HHI |
| R2-2207252 |
Design aspects of relay selection and reselection for U2U relay |
Ericsson |
| R2-2207278 |
Discovery and reselection with UE-to-UE relaying |
Intel Corporation |
| R2-2207336 |
Basic aspects for U2U Relay work |
Lenovo |
| R2-2207457 |
Discussion on U2U Relay Discovery and Relay (Re)-selection |
Apple |
| R2-2207520 |
Discussion on U2U Relay Discovery and (Re)selection |
CATT |
| R2-2207644 |
Discussion on mechanisms to support UE-to-UE relay |
China Telecom |
| R2-2207653 |
Consideration for UE-to-UE relay operation |
LG Electronics France |
| R2-2207686 |
Discussion on relay discovery and (re)selection for U2U relay |
Spreadtrum Communications |
| R2-2207729 |
Overall views on U2U sidelink relay |
Samsung R&D Institute UK |
| R2-2207838 |
UE-to-UE relay cell reselection and Relay UE DRX |
Sony |
| R2-2207860 |
Scenarios that require UE-to-UE relay (re)selection |
Sharp |
| R2-2207861 |
UE-to-UE relay discovery and (re)selection |
Sharp |
| R2-2208005 |
Clarifications on the scope of SL based U2U Relay |
Nokia, Nokia Shanghai Bell |
| R2-2208039 |
Initial considerations for U2U L2 relay CP operations |
Kyocera |
| R2-2208041 |
Initial considerations for U2U relay discovery and (re)selection |
Kyocera |
| R2-2208083 |
Discussion on L2 and L3 U2U relay |
vivo |
| R2-2208151 |
Discovery and Relay Selection for UE-to-UE Relays |
InterDigital |
| R2-2208427 |
Consideration on U2U relay |
CMCC |
| R2-2208489 |
Discussion on UE-to-UE relay |
Huawei, HiSilicon |
| 8.9.3 |
Service continuity enhancements for L2 UE-to-network relay |
|
| R2-2207078 |
Discussion on further enhancement of U2N service continuity |
OPPO |
| R2-2207133 |
Service continuity for UE-to-Network relay |
Qualcomm Incorporated |
| R2-2207169 |
Service Continuity Enhancement for Sidelink Relay |
MediaTek Inc. |
| R2-2207181 |
Discussion on service continuity enhancement |
Xiaomi |
| R2-2207199 |
Discussion on Service continuity enhancement for U2N relay |
ZTE |
| R2-2207220 |
Service Continuity Enhancements for Layer-2 UE-to-Network Relays |
Ericsson España S.A. |
| R2-2207279 |
Service continuity enhancements for L2 U2N relaying |
Intel Corporation |
| R2-2207420 |
Discussion on Service continuity enhancement of L2 U2N relay |
Apple |
| R2-2207521 |
Service Continuity Enhancements for L2 U2N Relay |
CATT |
| R2-2207642 |
Discussion on service continuity enhancements for L2 U2N relay |
China Telecom |
| R2-2207652 |
Service continuity enhancements for L2 U2N relay |
LG Electronics France |
| R2-2207687 |
Service continuity enhancements support for L2 U2N relay |
Spreadtrum Communications |
| R2-2207700 |
Discussion on Service continuity in U2N relay case |
Lenovo |
| R2-2207839 |
Service continuity enhancements for UE sidelink relay |
Sony |
| R2-2207963 |
Considerations on Service Continuity Enhancement |
NEC Corporation |
| R2-2208006 |
Discussion on service continuity enhancement for L2 U2N relay |
Nokia, Nokia Shanghai Bell |
| R2-2208082 |
On service continuity enhancement for L2 U2N relay |
vivo |
| R2-2208158 |
U2N Relay UE operation Threshold Conditions: Impact of UE Mobility |
Philips International B.V. |
| R2-2208229 |
Discussion on Service Continuity |
Huawei, HiSilicon |
| R2-2208260 |
Service continuity enhancement for L2 U2N relay |
Samsung |
| R2-2208428 |
Service continuity on U2N relay |
CMCC |
| 8.9.4 |
Multi-path relaying |
|
| R2-2207015 |
Discussion on multi-path SL relay |
OPPO |
| R2-2207137 |
Initial discussion on multi-path operation for UE-to-Network relay |
Qualcomm Incorporated |
| R2-2207180 |
Discussion on multi-path |
Xiaomi |
| R2-2207187 |
Initial consideration on the multi-path relaying |
ZTE, Sanechips |
| R2-2207221 |
Multipath Support with Direct path and Indirect path |
Ericsson España S.A. |
| R2-2207280 |
Discussion on Multi-path Relaying |
Intel Corporation |
| R2-2207361 |
Multipath support for remote UE |
MediaTek Beijing Inc. |
| R2-2207458 |
Discussion on multi-path support |
Apple |
| R2-2207522 |
Discussion on Multi-path |
CATT |
| R2-2207643 |
Discussion on multi-path support to enhance reliability and throughput |
China Telecom |
| R2-2207688 |
Discussion on multi-path relaying |
Spreadtrum Communications |
| R2-2207701 |
Discussion on Multi-path relaying |
Lenovo |
| R2-2207840 |
Multi-path relaying discussion |
Sony |
| R2-2207847 |
Discussion on multipath for sidelink relay enhancement |
Samsung |
| R2-2207862 |
benefit of multi-path relay |
Sharp |
| R2-2207964 |
Considerations on Multipath of Sidelink Relay |
NEC Corporation |
| R2-2208081 |
Multi-path UE aggregation on PC5 and Ideal-link |
vivo |
| R2-2208152 |
Scenarios, Use Cases, and Protocol Architecture for Multi-path |
InterDigital |
| R2-2208153 |
Design Aspects for Multi-path |
InterDigital |
| R2-2208154 |
Considerations on reliability and throughput for multi-path |
Nokia, Nokia Shanghai Bell |
| R2-2208349 |
Multi-path relaying for NR sidelink relay enhancements |
LG Electronics France |
| R2-2208429 |
Multi-path and UE aggregation |
CMCC |
| R2-2208488 |
Discussion on Rel-18 multi-path via SL relay and UE aggregation |
Huawei, HiSilicon |
| R2-2208809 |
[AT119-e][427][Relay] Handling of scenarios 1 and 2 (LG) |
LGE |
| 8.10.1 |
Organizational |
|
| R2-2207803 |
Work Plan for Rel-18 IDC |
Xiaomi |
| 8.10.2 |
FDM solution enhancements |
|
| R2-2207161 |
Clarification on the IDC scope |
ZTE Corporation, Sanechips |
| R2-2207162 |
Consideration on the FDM enhancement |
ZTE Corporation, Sanechips |
| R2-2207469 |
Discussion on FDM solution enhancements for IDC |
OPPO |
| R2-2207539 |
Discussion on FDM solution enhancements |
Sharp |
| R2-2207556 |
Assistance information for FDM |
Nokia, Nokia Shanghai Bell |
| R2-2207804 |
Discussion on the IDC FDM solutions |
Xiaomi |
| R2-2207844 |
Discussion on FDM solution for in-device co-existence interference avoidance |
Samsung |
| R2-2207936 |
Discussion on FDM solution in IDC |
Apple |
| R2-2207968 |
Enhanced FDM solution for IDC |
Intel Corporation |
| R2-2208116 |
FDM Solutions in IDC |
Qualcomm Incorporated |
| R2-2208135 |
FDM solution for IDC |
Ericsson |
| R2-2208230 |
Discussion on FDM enhancement |
Huawei, HiSilicon |
| R2-2208396 |
Discussion on FDM solution for R18 IDC |
vivo |
| R2-2208524 |
IDC FDM solution |
LG Electronics |
| R2-2208694 |
Discussion on FDM solution enhancements for IDC |
OPPO |
| R2-2208951 |
Report of [AT119-e] [615] [IDC] FDM solution enhancements |
Huawei, HiSilicon |
| 8.10.3 |
TDM solution |
|
| R2-2207379 |
TDM Assistance Information for IDC |
Nokia, Nokia Shanghai Bell |
| R2-2207718 |
TDM solution for IDC problem |
Lenovo |
| R2-2207805 |
Candidate TDM solutions for IDC |
Xiaomi |
| R2-2207845 |
Discussion on TDM solution for in-device co-existence interference avoidance |
Samsung |
| R2-2207937 |
Discussion on TDM solution in IDC |
Apple |
| R2-2207969 |
TDM solution for IDC |
Intel Corporation |
| R2-2208113 |
TDM Solution for NR IDC |
Ericsson |
| R2-2208118 |
TDM Solutions in IDC |
Qualcomm Incorporated |
| R2-2208231 |
Discussion on TDM solution for NR IDC |
Huawei, HiSilicon |
| R2-2208397 |
Discussion on TDM solution for IDC |
vivo |
| R2-2208525 |
IDC TDM solution |
LG Electronics |
| R2-2208952 |
Summary of [AT119-e][652][IDC] TDM solution (Xiaomi) |
Xiaomi |
| 8.11.1 |
Organizational |
|
| R2-2206965 |
UE capabilities for MBS (S2-2203020; contact: Qualcomm) |
SA2 |
| R2-2206973 |
Reply LS on UE capabilities for MBS (RP-221861; contact: Qualcomm) |
RAN |
| R2-2207770 |
Rel-18 NR MBS enhancement workplan |
CATT |
| R2-2209193 |
LS on FS_5MBS_Ph2 progress (S2-2207470; contact: Huawei) |
SA2 |
| 8.11.2 |
Multicast reception in RRC_INACTIVE |
|
| R2-2206987 |
Discussion on supporting group scheduling for RRC_INACTIVE UEs |
FGI |
| R2-2206988 |
Multicast reception in RRC_INACTIVE state |
TD Tech Ltd |
| R2-2206997 |
Discussion on multicast reception in RRC_INACTIVE state |
OPPO |
| R2-2207047 |
Considerations for Multicast Reception in RRC_INACTIVE |
Samsung |
| R2-2207191 |
Discussion on RAN based Notification Area for Multicast Mobility in RRC Inactive State |
TCL Communication Ltd. |
| R2-2207204 |
Overview considerations on Multicast reception in RRC_INACTIVE |
NEC Europe Ltd |
| R2-2207227 |
Supporting Multicast Reception in RRC_INACTIVE |
vivo |
| R2-2207318 |
Discussion on possible approaches to support multicast for inactive UEs |
Futurewei |
| R2-2207412 |
State transition for UEs receiving Multicast in RRC_INACTIVE state |
TCL Communication Ltd. |
| R2-2207415 |
PTM configuration for UEs receiving Multicast in RRC_INACTIVE state |
TCL Communication Ltd. |
| R2-2207447 |
Multicast reception in RRC_INACTIVE state |
Apple |
| R2-2207481 |
Considerations on the multicast reception in RRC_INACTIVE |
Beijing Xiaomi Software Tech |
| R2-2207557 |
MBS inactive principles |
Nokia, Nokia Shanghai Bell |
| R2-2207566 |
Discussion on multicast enhancement for RRC INACTIVE state |
MediaTek inc. |
| R2-2207588 |
Multicast reception in RRC_INACTIVE |
Huawei, HiSilicon |
| R2-2207689 |
Discussion on Multicast Reception in RRC_INACTIVE |
Spreadtrum Communications |
| R2-2207698 |
PTM configuration for multicast reception in RRC_INACTIVE |
Lenovo |
| R2-2207699 |
Mobility and state transition for multicast reception in RRC_INACTIVE |
Lenovo |
| R2-2207720 |
Mobility of UEs receiving multicast in RRC_INACTIVE state |
CANON Research Centre France |
| R2-2207730 |
PTM Configuration in RRC_INACTIVE |
SHARP Corporation |
| R2-2207771 |
Discussion on multicast reception in RRC_INACTIVE |
CATT, CBN |
| R2-2208093 |
MBS multicast reception in RRC_INACTIVE |
Ericsson |
| R2-2208096 |
Multicast reception by UEs in RRC_INACTIVE state |
Qualcomm Incorporated |
| R2-2208289 |
Multicast reception in RRC INACTIVE |
Kyocera |
| R2-2208312 |
Multicast reception in RRC_INACTIVE |
LG Electronics Inc. |
| R2-2208374 |
MBS support in RRC_INACTIVE |
InterDigital, Inc. |
| R2-2208441 |
Initial consideration on multicast reception in RRC_INACTIVE |
CMCC |
| R2-2208499 |
Multicast reception in RRC_INACTIVE |
Intel Corporation |
| R2-2208520 |
Discussion on user plane aspects for support of multicast in RRC_INACTIVE |
LG Electronics Inc. |
| R2-2208633 |
Multicast reception in RRC_INACTIVE |
ZTE, Sanechips |
| 8.11.3 |
Shared processing for MBS broadcast and Unicast reception |
|
| R2-2206989 |
Simultaneous unicast reception and MBS broadcast reception |
TD Tech Ltd |
| R2-2206990 |
A new MCCH transmission method |
Chengdu TD Tech, TD Tech |
| R2-2206991 |
MBS reception interruption problem in LTE and NR |
TD Tech Ltd |
| R2-2206998 |
Discussion on support of FTA in NR |
OPPO |
| R2-2207014 |
MBS reception interruption problem in LTE and NR |
Chengdu TD Tech, TD Tech |
| R2-2207184 |
Discussion on UE shared Processing for Broadcast and Unicast Services Reception |
TCL Communication Ltd. |
| R2-2207228 |
Supporting Shared Processing for MBS Broadcast and Unicast |
vivo |
| R2-2207448 |
Sharing processing of MBS broadcast and unicast reception |
Apple |
| R2-2207567 |
Discussion on broadcast coexistence and signaling enhancement |
MediaTek inc. |
| R2-2207589 |
Discussion on shared processing for MBS broadcast and unicast reception |
Huawei, CBN, HiSilicon |
| R2-2207690 |
Discussion on shared processing for MBS broadcast and Unicast Reception |
Spreadtrum Communications |
| R2-2207772 |
Discussions on shared processing for MBS broadcast and unicast reception |
CATT, CBN |
| R2-2207808 |
Discussion on shared processing for MBS broadcast and unicast reception |
Xiaomi |
| R2-2208092 |
MBS broadcast and unicast reception with shared resources |
Ericsson |
| R2-2208097 |
Shared processing for MBS broadcast and unicast reception |
Qualcomm Incorporated |
| R2-2208182 |
Shared processing for MBS broadcast and unicast reception |
Nokia, Nokia Shanghai Bell |
| R2-2208290 |
Shared processing for simultaneous reception of MBS and unicast |
Kyocera |
| R2-2208442 |
Discussion on shared processing for broadcast and unicast reception |
CMCC |
| R2-2208548 |
Shared processing for simultaneous MBS broadcast and Unicast reception |
Intel Corporation |
| R2-2208591 |
Uu Signaling Enhancements for MBS |
Samsung |
| R2-2208634 |
On shared processing for MBS broadcast and Unicast reception |
ZTE, Sanechips |
| 8.12 |
Mobile IAB (Integrated Access and Backhaul) for NR |
|
| R2-2209090 |
Summary of offline [AT119-e][031][IAB18] (Qualcomm) |
Qualcomm |
| 8.12.1 |
Organizational |
|
| R2-2207282 |
Workplan for Rel-18 mobile IAB |
Qualcomm Inc. (Rapporteur) |
| 8.12.2 |
Mobility Enhancements |
|
| R2-2207121 |
Mobility Enhancement of mobile IAB-node and served UEs |
Intel Corporation |
| R2-2207128 |
Mobile IAB mobility enhancement |
Huawei, HiSilicon |
| R2-2207186 |
Discussion on group mobility of UEs served by mobile IAB |
ZTE, Sanechips |
| R2-2207283 |
Enhancements for IAB-node mobility |
Qualcomm Inc. |
| R2-2207421 |
Discussion on mobility enhancement in mobile IAB |
Apple |
| R2-2207708 |
Mobility enhancements for mobile IAB-node and its served UE |
Lenovo |
| R2-2207816 |
Discussion on the enhancement of IAB node mobility |
Samsung R&D Institute UK |
| R2-2207826 |
Mobility enhancement for mobile IAB |
Sony |
| R2-2208103 |
Mobility enhancements for mIAB node |
Ericsson |
| R2-2208242 |
IAB mobility |
Nokia, Nokia Shanghai Bell |
| R2-2208267 |
Mobility state of an IAB cell |
InterDigital, Inc. |
| R2-2208268 |
Group mobility in mobile IAB |
InterDigital, Inc. |
| R2-2208292 |
UE handover aspects for mobile IAB |
Kyocera |
| R2-2208459 |
Discussion on mobile IAB |
vivo |
| R2-2208523 |
Concurrent UE handovers resulting from IAB node full migration |
LG Electronics |
| 8.12.3 |
Other |
|
| R2-2207122 |
Discussion on Migration and PCI handling of mobile IAB-node |
Intel Corporation |
| R2-2207124 |
Discussion on multi-hop scenario for mobile IAB-node |
Intel Corporation, Qualcomm, Huawei, Ericsson, Nokia, InterDigital |
| R2-2207129 |
Full migration and interference mitigation |
Huawei, HiSilicon |
| R2-2207185 |
Discussion on topology adaptation in mobile IAB scenario |
ZTE, Sanechips |
| R2-2207284 |
Other enhancements for mobile IAB |
Qualcomm Inc. |
| R2-2207422 |
Discussion on RAN2 aspects of inter-donor full migration and mitigation of interference in mobile IAB |
Apple |
| R2-2207627 |
mIAB - other key issues |
Samsung R&D Institute UK |
| R2-2207709 |
Discussion on inter-donor full migration of mobile IAB |
Lenovo |
| R2-2207827 |
PCI collision in mobile IAB |
Sony |
| R2-2208104 |
On Migration and Interference mitigation |
Ericsson |
| R2-2208243 |
On mobile IAB deployment and interference mitigation |
Nokia, Nokia Shanghai Bell |
| R2-2208251 |
Consideration on PCI collisions for Mobile IAB |
Sharp |
| R2-2208291 |
Scenarios on mobile IAB topology |
Kyocera |
| R2-2208514 |
Consideration on potential complexity of a scenario |
LG Electronics Inc. |
| 8.13.1 |
Organizational |
|
| R2-2208452 |
Work plan for Further Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI |
CMCC |
| R2-2209104 |
LS on the scope for the support of SON/MDT enhancements (R3-225238; contact: Nokia) |
RAN3 |
| R2-2209105 |
LS on NR-U support for MRO (R3-225241; contact: Ericsson) |
RAN3 |
| 8.13.2 |
Data collection for MRO for MR DC SCG failure and Inter-system handover for voice fallback. |
|
| R2-2207093 |
Discussion on MRO of inter-system HO voice fallback |
OPPO |
| R2-2207192 |
Discussion on MRO enhancement for inter-system handover for voice fallback |
NTT DOCOMO, INC. |
| R2-2207193 |
Discussion on MRO for MR-DC SCG failure scenario and fast MCG recovery failure |
NTT DOCOMO, INC. |
| R2-2207476 |
Data for MRO related Enhancements |
CATT |
| R2-2207704 |
MRO for inter-system handover for voice fallback |
Lenovo |
| R2-2207954 |
Discussion on the inter-system handover for voice fallback |
Huawei, HiSilicon |
| R2-2207955 |
Discussion on MR-DC SCG failure |
Huawei, HiSilicon |
| R2-2208157 |
Data collection for MRO for MR-DC SCG failures and inter-system handover for voice fallback |
Qualcomm Incorporated |
| R2-2208177 |
On Mobility Robustness Optimization |
Ericsson |
| R2-2208436 |
Discussion on inter-system handover for voice fallback |
CMCC |
| R2-2208542 |
Consideration on MRO for EPS fallback via HO and MRDC SCG failure |
ZTE Corporation, Sanechips |
| R2-2208583 |
Discussion on MRO for MR-DC SCG failure and inter-system handover voice fallback |
Xiaomi |
| R2-2208610 |
UE reporting to enhance mobility parameter tuning |
Samsung R&D Institute India |
| R2-2208930 |
(reserved)[Pre119-e][R18 SONMDT] Pre-meeting summary of 8.13.2 (Ericsson) |
Ericsson |
| 8.13.3 |
Miscellaneous SON MDT enhancements |
|
| R2-2207091 |
Discussion of SON on MR-DC CPAC |
OPPO |
| R2-2207092 |
SON on fast MCG recovery |
OPPO |
| R2-2207196 |
Discussion on SON for MR-DC CPAC |
NTT DOCOMO, INC. |
| R2-2207437 |
SON enhancements for NR-U |
Apple |
| R2-2207438 |
SON enhancements for RACH partitioning |
Apple |
| R2-2207477 |
General Considerations on SON MDT enhancements |
CATT |
| R2-2207478 |
Discussion on CPAC and Successful Report for Inter-RAT Handover and PSCell Change |
CATT |
| R2-2207705 |
SON enhancements for CPC and fast MCG link recovery |
Lenovo |
| R2-2207706 |
SON enhancements for successful PSCell change report and SHR for inter-RAT HO |
Lenovo |
| R2-2207707 |
MRO for handover failure or SCG failure in NR-U |
Lenovo |
| R2-2207721 |
Discussion on the SON/MDT enhancement for NPN and RACH report |
Beijing Xiaomi Software Tech |
| R2-2207908 |
SONMDT enhancements for RACH enhancements |
NEC |
| R2-2207909 |
Discussion on successful PSCell change report |
NEC |
| R2-2207956 |
Discussion on other SON enhancements |
Huawei, HiSilicon |
| R2-2208066 |
Discussion on CPAC failure information |
vivo |
| R2-2208067 |
Discussion on successful PSCell change report |
vivo |
| R2-2208068 |
Discussion on RACH report enhancement |
vivo |
| R2-2208159 |
Miscellaneous SON MDT enhancements |
Qualcomm Incorporated |
| R2-2208160 |
SON enhancements for NR-U |
Qualcomm Incorporated |
| R2-2208176 |
SON support for NPN |
Ericsson |
| R2-2208178 |
Supporting NR-U in the SON/MDT framework |
Ericsson |
| R2-2208244 |
Impact of SNPN on MDT and MRO |
Nokia, Nokia Shanghai Bell |
| R2-2208245 |
RACH report related enhancements and Fast MCG recovery optimizations |
Nokia, Nokia Shanghai Bell |
| R2-2208246 |
MRO enhancements for NR-U |
Nokia, Nokia Shanghai Bell |
| R2-2208285 |
SON aspects for fast MCG recovery |
Sharp |
| R2-2208433 |
SONMDT enhancement for fast MCG recovery and RACH report |
CMCC |
| R2-2208434 |
Discussion on Successful PSCell change report |
CMCC |
| R2-2208435 |
SON MDT enhancement for CPA and CPC |
CMCC |
| R2-2208543 |
Consideration on miscellaneous issues on SON aspects |
ZTE Corporation, Sanechips |
| R2-2208544 |
Consideration on miscellaneous issues on MDT aspects |
ZTE Corporation, Sanechips |
| R2-2208572 |
SON/MDT enhancements for dual connectivity scenarios |
Samsung R&D Institute India |
| R2-2208584 |
Discussion on Miscellaneous SON MDT enhancements |
Xiaomi |
| R2-2208603 |
Various SON/MDT Enhancements |
Samsung R&D Institute India |
| R2-2208661 |
Discussion on UE RACH report enhancements |
China Telecom |
| R2-2208904 |
Pre-meeting summary of 8.13.3 |
Huawei |
| R2-2208939 |
Pre-meeting summary of 8.13.3 |
Huawei |
| R2-2209024 |
LS on SN RACH report status in R17 |
RAN2 |
| 8.13.4 |
Other |
|
| R2-2207479 |
Consideration on Inter-RAT Signaling Based Logged MDT Override Protection |
CATT |
| R2-2207480 |
Considerations on the signaling based logged MDT override protection for E-UTRAN |
Beijing Xiaomi Software Tech |
| R2-2207957 |
Discussion on the inter-system signalling based MDT override protection |
Huawei, HiSilicon |
| R2-2208161 |
Signalling based logged MDT override protection |
Qualcomm Incorporated |
| R2-2208179 |
inter-RAT signalling based logged MDT protection |
Ericsson |
| R2-2208247 |
Signalling based logged MDT override protection in Rel-18 |
Nokia, Nokia Shanghai Bell |
| R2-2208535 |
Inter-RAT signaling based logged MDT override protection |
Samsung R&D Institute India |
| R2-2208536 |
Inter-RAT signaling based logged MDT override protection |
Samsung R&D Institute India |
| R2-2208545 |
Consideration on Signalling based MDT protection |
ZTE Corporation, Sanechips |
| R2-2208698 |
Summary on 8.13.4: Inter-RAT signalling based logged MDT protection |
Nokia, Nokia Shanghai Bell |
| R2-2208933 |
Summary on 8.13.4: Inter-RAT signalling based logged MDT protection |
Nokia, Nokia Shanghai Bell |
| 8.14.1 |
Organizational |
|
| R2-2208619 |
Work Plan for Rel-18 NR QoE Enhancement |
China Unicom |
| R2-2209103 |
LS to SA4 on Rel-18 enhancement of NR QoE (R3-225227; contact: Huawei) |
RAN3 |
| R2-2209109 |
LS to RAN2 on RAN3 agreement of QoE reporting in NR-DC (R3-225256; contact: China Unicom) |
RAN3 |
| 8.14.2 |
QoE measurements in RRC_IDLE INACTIVE |
|
| R2-2207026 |
QoE measurement collection for IDLE and Inactive state |
Qualcomm Incorporated |
| R2-2207427 |
IDLE/INACTIVE Mode QoE Measurements and Reporting |
Apple |
| R2-2207532 |
Considerations on QoE measurements in RRC_IDLE and RRC_INACTIVE |
Lenovo |
| R2-2207725 |
Discussion on QoE for MBS |
Ericsson |
| R2-2207822 |
Discussion on MBS broadcast services |
CATT |
| R2-2207992 |
QoE measurements for MBS broadcast services |
Huawei, HiSilicon |
| R2-2208248 |
QMC enhancements for NR MBS |
Nokia, Nokia Shanghai Bell |
| R2-2208391 |
QoE measurement in RRC_IDLE and RRC_INACTIVE |
Samsung |
| R2-2208423 |
Discussion on QoE measurement in RRC_IDLE and RRC_INACTIVE |
CMCC |
| R2-2208615 |
Discussion on Rel-18 QoE measurement |
ZTE Corporation, Sanechips |
| R2-2208622 |
Discussion on MBS configuration and reporting for NR QoE in Rel-18 |
China Unicom |
| 8.14.3 |
Rel-17 leftover topics for QoE |
|
| R2-2207027 |
Discussion on Rel-17 leftover issues |
Qualcomm Incorporated |
| R2-2207428 |
Views on Potential Enhancements of Existing QoE Features |
Apple |
| R2-2207533 |
Discussion on Rel-17 leftover features for QoE |
Lenovo |
| R2-2207724 |
Discussion on rel-17 leftovers |
Ericsson |
| R2-2207823 |
Discussion on Rel-17 leftover issues for QoE |
CATT |
| R2-2207993 |
Support of left-over features from Rel-17 |
Huawei, HiSilicon |
| R2-2208249 |
QMC enhancements for RAN overload |
Nokia, Nokia Shanghai Bell |
| R2-2208392 |
Timing information of measured samples |
Samsung |
| R2-2208616 |
Discussion on Rel-17 leftover issues for QoE |
ZTE Corporation, Sanechips |
| 8.14.4 |
Other topics |
|
| R2-2208613 |
Recommended bitrate for XR services |
MediaTek Beijing Inc. |
| R2-2208629 |
On RAN visible QoE parameters for new services |
China Telecom |
| 8.15 |
R18 Other |
|
| R2-2206962 |
LS on Rel-18 WI related to vehicular distributed antenna systems (S-220026; contact: LGE) |
S4SEM |
| R2-2206963 |
LS on RAN feedback for low latency (S2-2201767; contact: Huawei) |
SA2 |
| R2-2206967 |
LS On FS_REDCAP_Ph2 option feasibility (S2-2204989; contact: Ericsson) |
SA2 |
| R2-2206976 |
LS out on authenticity and replay protection of system information (S3-221700; contact: CableLabs) |
SA3 |
| R2-2207028 |
Draft Reply LS on authenticity and replay protection of system information |
Samsung |
| R2-2207043 |
Draft reply LS on RAN feedback for low latency |
Qualcomm Incorporated |
| R2-2207167 |
CR on 38331 for SFN-DFN offset and PosSIB request |
MediaTek Inc. |
| R2-2207168 |
Positioning support for remote UEs |
MediaTek Inc. |
| R2-2207287 |
Positioning support for remote UEs |
MediaTek Inc., CATT |
| R2-2207288 |
Downlink positioning support and posSIB request for L2 UE-to-network remote UE |
MediaTek Inc., CATT |
| R2-2207289 |
Indication to LMF of operation as a L2 UE-to-network remote UE |
MediaTek Inc., CATT |
| R2-2207290 |
Positioning method support for L2 UE-to-network remote UE |
MediaTek Inc., CATT |
| R2-2207623 |
Discussion on the SA2 LS “FS_REDCAP_Ph2 option feasibility” for RRC_INACTIVE eDRX |
Huawei, HiSilicon |
| R2-2207768 |
Consideration on meeting very low latency requirement in TDD |
ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2207775 |
[DRAFT] Reply LS on RAN feedback for low latency |
ZTE Corporation, Sanechips |
| R2-2208007 |
Proposed response to SA2 LS R2-2203930 on low latency |
Nokia, Nokia Shanghai Bell |
| R2-2208107 |
Consideration on Rel-18 UL Tx switching capability |
ZTE Corporation, Sanechips |
| R2-2208134 |
Discussion on RAN feedback for low latency |
Ericsson |
| R2-2208216 |
CFRA resources for Conditional Handover |
Nokia, Nokia Shanghai Bell |
| R2-2208314 |
Positioning support for remote UEs |
MediaTek Inc., CATT, Huawei, HiSilicon |
| R2-2208315 |
Downlink positioning support and posSIB request for L2 UE-to-network remote UE |
MediaTek Inc., CATT, Huawei, HiSilicon |
| R2-2208317 |
Indication to LMF of operation as a L2 UE-to-network remote UE |
MediaTek Inc., CATT, Huawei, HiSilicon |
| R2-2208319 |
Positioning method support for L2 UE-to-network remote UE |
MediaTek Inc., CATT, Huawei, HiSilicon |
| R2-2208324 |
Potential issues on UL Tx switching schemes across up to 3 or 4 bands |
NTT DOCOMO INC. |
| R2-2208327 |
Work plan for Multi-carrier enhancements |
NTT DOCOMO INC. |
| R2-2208460 |
Protection of system information |
vivo |
| R2-2208481 |
RAN2 impact to support Rel-18 UL Tx switching enhancements |
Huawei, HiSilicon |
| R2-2208482 |
Discussion on authenticity and replay protection of system information(SA3 LS) |
Huawei, HiSilicon |
| R2-2208490 |
Discussion on RAN Aspects of Signal Level Enhanced Network Selection |
Huawei, HiSilicon |
| R2-2208568 |
Discussion on solutions for eDRX cycle beyond 10.24s for RedCap |
ZTE Corporation, Sanechips |
| R2-2208625 |
Discussion on system information security |
Ericsson |
| R2-2208687 |
Discussion on RAN feedback for low latency enquired by SA2 |
Huawei |
| R2-2208688 |
Draft reply LS on RAN feedback for low latency |
Huawei |
| R2-2208913 |
Reply LS on RAN feedback for low latency |
RAN2 |
| R2-2208914 |
Summary of [AT119-e][310][R18 Others - Low Latency] LS on Low latency (Huawei) |
Huawei, HiSilicon |
| R2-2208936 |
Summary of [AT119-e][026][NR18] UL Tx Switching (NTT Docomo) |
NTT DOCOMO INC. (Moderator) |
| R2-2208959 |
Report of [AT119-e][025][NR18] Protection of SI (Samsung) |
Samsung |
| R2-2208960 |
Reply LS on authenticity and replay protection of system information |
Samsung |
| R2-2208985 |
Reply LS on authenticity and replay protection of system information |
RAN2 |
| R2-2209015 |
Reply LS on FS_REDCAP_Ph2 option feasibility (R3-225119; contact: ZTE) |
RAN3 |
| R2-2209017 |
Reply LS on UL Tx switching across 3 or 4 bands (R4-2214464; contact: China Telecom) |
RAN4 |
| R2-2209115 |
Report from [AT119-e][024][NR18] FS_REDCAP_Ph2 option feasibility (Ericsson) |
Ericsson (Rapporteur) |
| R2-2209150 |
LS to RAN2 on two overlapping LTE-CRS patterns in Rel-18 DSS (R1-2208194; contact: ZTE) |
RAN1 |
| R2-2209170 |
LS on extending the maximum range for NS values (R4-2214953; contact: Apple) |
RAN4 |
| R2-2209187 |
LS on FS_VMR solutions review (S2-2207070; contact: Qualcomm) |
SA2 |
| R2-2209188 |
LS on Terminology Alignment for Ranging/Sidelink Positioning (S2-2207129; contact: Xiaomi) |
SA2 |
| R2-2209192 |
LS Out on RAN dependency of FS_eNS_Ph3 (S2-2207435; contact: ZTE) |
SA2 |
| R2-2209202 |
LS on starting a timer in RRC-inactive state (C1-225319; contact: Huawei) |
CT1 |
| R2-2209203 |
LS on SENSE feature (C1-225338; contact: Huawei) |
CT1 |
| R2-2209243 |
Reply LS on FS_REDCAP_Ph2 option feasibility |
RAN2 |
| 9.1 |
Session on NTN, IoT NTN, RedCap and CE |
|
| R2-2208701 |
Report from Break-Out Session on NTN, IoT NTN, RedCap and CE |
Vice Chairman (ZTE) |
| 9.2 |
Session on LTE legacy, 71 GHz, DCCA, Multi-SIM, RAN slicing, QoE and XR |
|
| R2-2208702 |
Report from session on LTE legacy, 71 GHz, DCCA, Multi-SIM, RAN slicing, QoE and XR |
Vice Chairman (Nokia) |
| 9.3 |
Session on UP, Small data, URLLC/IIoT, RACH indication, NWES and UAV |
|
| R2-2208703 |
Report from UP, Small data, URLLC/IIoT, RACH indication, NWES and UAV |
Session chair (InterDigital) |
| 9.4 |
Session on positioning and sidelink relay |
|
| R2-2208704 |
Report from session on positioning and sidelink relay |
Session chair (MediaTek) |
| 9.5 |
Session on LTE V2X and NR SL |
|
| R2-2208705 |
Report from session on LTE V2X and NR SL |
Session chair (Samsung) |
| 9.6 |
Session on SON/MDT |
|
| R2-2208706 |
Report from SON/MDT session |
Session chair (CMCC) |
| 9.7 |
Session on MBS |
|
| R2-2208707 |
Report from MBS breakout session |
Session chair (Huaweil) |
| 9.8 |
Session on IDC |
|
| R2-2208708 |
Report from IDC breakout session |
Session chair (Intel) |
| 9.9 |
Session on NC Repeater |
|
| R2-2208709 |
Report from NC Repeater breakout session |
Session chair (Apple) |